.theseoINSTITUTE FOR VISIBILITY
About this choice

We only save your display preference in a preference cookie, for up to 180 days on this device. No CRM or advertising data. Your tracking consent stays unchanged. If cookies are blocked, your choice may not be saved.

Discover
Close

MyParcel Dashboard · IN SHORT

Several online shops.One working view.A clear view.

MyParcel Dashboard by TheSEO brings shipment follow-up into one working view: delays, returns, team notes and damage files alongside the parcel. It is an independent product, with no official MyParcel affiliation. MyParcel remains the source of your shipping arrangements, labels and carrier statuses.

Independent of MyParcel · public preview with fictional sample data

Try the demoExplore what matters
Illustration of a tablet with abstract shipment cards, two shipping boxes and a silver scanner.
VISUAL IMPRESSION · MYPARCEL DASHBOARD

For teams working across several shops

MyParcel already supports several online shops. This dashboard adds a place to organise the follow-up: which parcel needs attention, what a colleague has already done and which file is still open.

That can be useful when several people monitor shipments across shops. If one quiet shop is easy to manage in the existing MyParcel overview, an additional dashboard may add little. It is not a stock, order-picking or warehouse system.

Six workspaces for different moments

Announced highlights parcels that have gone more than 48 hours without progress, with status filters and parcel history. Shipped brings tracking statuses together and lets the team keep notes, retrieve available customs documents and export a selection as CSV. Returns separates incoming return parcels from the outgoing flow. Shops holds the connected shops, MyParcel keys and plan limits. Damage files collect the amount, notes, status and carrier deadline from Growth upwards. A prepared claim email still needs handling; it is not an automatically submitted or accepted claim. Analysis provides views over 30, 60 or 90 days, including delivery times, volume and performance by shop. The wallboard displays the overview on a shared screen. These are your operation's figures when connected, not a benchmark or a promise of faster delivery.

Announced

Find parcels announced more than 48 hours ago without progress. Filter, search and open the parcel detail to see its status history.

Shipped

Review delivered, in-transit and delayed parcels. Keep team notes with the shipment, look up customs documents and export a selection as CSV.

Returns

Separate return parcels from the outgoing flow. See which are still coming back and which have arrived, with their parcel history.

Online shops

Manage connected shops, MyParcel keys and plan limits. The renewed branding and customer-email chain is not yet released as a completed feature.

Damages

Keep the amount, notes, status and carrier deadline together. Included from Growth upwards, not in Starter. A drafted claim email is not an automatically sent or accepted claim.

Analysis

Review patterns over 30, 60 or 90 days, including delivery times and shop performance. The wallboard shows the picture on a shared screen. Example figures are not customer results.

INTERACTIVE DESIGN PREVIEW

Your shipping work in one workspace.

Try the overview with shipment statuses, shipping volume and an action list. The frame below opens the existing dashboard design preview.

  • Overview
  • Shipment statuses
  • Action list

Interactive design preview. Fictional data, no production actions. The backend is not connected. This is not a connected CRM or shipping environment.

Open the demo in a new tab

The demo interface is in Dutch. On a small screen, you can also open it in a new tab.

Dutch-language MyParcel design with fictional shipments on desktop
MyParcel dashboard / design preview

Compare capacity and synchronisation

Starter is €35 per month for up to 40 shops, with a 30-minute synchronisation interval. Growth is €79.99 for up to 80 shops, with a 15-minute interval and damage files. Pro is €149 for up to 250 shops, with a 10-minute interval. Enterprise is €249.99 with a five-minute interval; its advertised unlimited capacity has a technical ceiling of 9,999 shops. These are dashboard charges, separate from shipping labels and carrier costs. A shorter interval refreshes the dashboard sooner; it does not change how quickly a carrier scans or delivers a parcel. Confirm the final total and VAT treatment before payment. Monthly cancellation is the public starting position unless both parties sign a different agreement. Automatic checkout remains closed. The plan selector prepares an enquiry, so selecting a plan does not charge you or activate an account.

Starter

€35per month

  • Up to 40 online shops
  • Every 30 minutes
  • An overview for a compact team.
  • Damage files are not included.
Starter plan check (Dutch)

Growth

€79.99per month

  • Up to 80 online shops
  • Every 15 minutes
  • For an operation with more daily volume.
  • Damage files with carrier deadlines.
Growth plan check (Dutch)

Pro

€149per month

  • Up to 250 online shops
  • Every 10 minutes
  • For teams managing several shops throughout the day.
  • Damage files are included.
Pro plan check (Dutch)

Enterprise

€249.99per month

  • Marketed as unlimited; technical ceiling 9,999 shops
  • Every 5 minutes
  • For larger environments and guided setup.
  • Damage files are included.
Enterprise plan check (Dutch)

The English source publishes these four monthly amounts and limits, with its verification date of 28 July 2026. The final total and VAT treatment must be confirmed before payment. Automatic checkout is still closed.

Monthly cancellation is the public starting position unless an agreement signed by both parties says otherwise. Damage files start at Growth, not Starter. The renewed customer-email chain remains behind a release gate.

The pricing, security, plan-selection and existing-account destinations below are in Dutch. The public preview is also in Dutch; this English explanation does not change the application language.

Read prices and terms (Dutch)

Check the open conditions before connecting data

The renewed branding and customer-email chain is not yet released as a completed feature. Payment remains closed while the required checks are outstanding, including VAT treatment, payment events, organisation isolation and the customer portal. There is no promised opening date.

Agree the retention period for your organisation before supplying real shipment data. A historical duration in the English explanation should not be treated as a final data-retention agreement while the security conditions are still being established.

This layer creates no shipping labels, negotiates no rates and does not replace customer service. A damage deadline depends on the carrier and circumstances; a file helps you follow the process but cannot guarantee compensation.

How it works (Dutch)Security status (Dutch)

Discuss the shops you need to manage

For a new enquiry, describe the shops, shipment volume, people following up parcels and the exceptions that are hardest to handle. Use the plan check to establish whether the product fits before arranging access.

Existing customers can use the published dashboard route. The application, deeper product pages and plan selection are in Dutch; this English explanation does not change their language.

Open the account-free preview (Dutch)Open the existing dashboard (Dutch)Choose a plan for review (Dutch)
Gianluca, founder of TheSEO

MEET THESEO

A question?
A direct line.

Working on websites and visibility since 2017. You speak directly with Gianluca.

Get in touch
All information

Explore the details at your own pace.

~/myparcel-dashboard · operational layer[ok] six workspaces
INS.MP01 · an operational layer for several online shops not a MyParcel product and no official affiliation with MyParcel

One MyParcel dashboard for several online shops.

For fulfilment teams and online shops with parcels spread across several shops. Six workspaces, exceptions at the top, notes and damage files in one place. MyParcel stays the source of your labels and your carriers; this layer makes the daily operation around them visible.

six workspacesin daily use by uspreview without an accountmonthly cancellation as the starting position
Open the preview → See the six workspaces Start the plan check the preview works without an account
INDEPENDENTdeveloped independently by TheSEOMyParcel stays the source of your labels and your carriers
overview how it works pricing security documentation demo get started NL
● MP / OPS
Search for a parcel, order or online shop…
GL

Workspace

Overview
Announced
Shipped
Returns
Online shops
Damages
Analysis

Administration

Settings

Parcel overview

LAST SYNC · 2 MIN AGO
IN TRANSIT47 +8
DELAYED6 WATCH
ACTION NEEDED3 OPEN
PARCELS · 7 DAYSFICTIONAL SAMPLE DATA
Online shopOrderStatus
Nordic Living#NL-2948In transit
Studio Groen#SG-1831Delayed
Buitenpost#BP-7720Delivered
3 parcels are asking for follow-up
PAIN.MP01 · the morning round

Separate accounts, separate tabs, the same question.

Several online shops means several places to look. The problem is not the time that costs, but what you fail to find with it.

Anyone running one online shop has one overview and one tab. Anyone running three, eight or forty has a ritual. You open the back office per shop, you scroll through yesterday's parcels, you click open the separate tracking pages of the carriers, and meanwhile your inbox fills with questions you can only answer after looking somewhere else.

The painful part is not the clicking. It is that the most important parcels are exactly the ones that fall away in a round like that. A parcel announced on Thursday that still has no first scan on Monday stands out in no separate overview, because in every separate overview it is one line among hundreds that look just like it. You see it once the client emails. From that moment you are no longer following up, you are explaining.

You see the same pattern with damage. A damaged parcel arrives as a client email, someone says they will look at it, and after that it sinks into an inbox. Carriers work with deadlines within which you have to report damage. Anyone without a file that holds that deadline only notices afterwards that the report was too late. Carelessness is rarely the cause. Usually it is simply the absence of a place where such a file belongs.

And then there is the third pain, the team one. Two colleagues see the same delayed parcel and do not know from each other whether anything has been done. So the client gets called twice, or not at all. There is no shared status, only a shared suspicion.

FIG.MP01: the morning round without a shared overviewschematic example
morning · manual round past separate sourcesfictional
08:12back office shop 1 · scrolling through yesterday's parcelsno signal
08:19back office shop 2 · same list, different shopno signal
08:26back office shop 3 · same list, different shopno signal
08:35inbox · "where is my parcel" · searching on an order numberreactive
08:41carrier tracking page · a separate page per parcelreactive
08:52damage spreadsheet · the carrier deadline is not in itrisk
Unanswered: which parcels are asking for action today, across all the shops?no answer

A schematic example of a manual round. The times and shops are fictional and illustrate the order, not a measured way of working.

SCOPE.MP01 · position in your chain

Between your MyParcel account and a warehouse system.

Honest about what already exists: MyParcel itself supports several online shops in one account. The difference is in what you do with the parcels afterwards.

FIG.MP02: three layers, three responsibilitiesschematic example
stays the source

MyParcel and the carriers

The shipping contract, labels, rates, collection and the scans on the way. Everything that physically puts a parcel in motion and the statuses that come out of it.

this layer

MyParcel Dashboard from TheSEO

Every connected shop in one picture, exceptions at the top, notes and follow-up at the parcel, damage files with the deadline in them, and analysis across the shops.

a different category

A warehouse system or WMS

Stock, order picking, warehouse locations and purchasing. If that is what you are after, you belong with a WMS. We do not do it and we do not pretend to.

This page starts with what already exists, because otherwise the story does not hold. MyParcel can hang several online shops under one account itself. If all you want is to make labels for three shops, you need nothing here. You feel the difference the moment those parcels have to be watched daily by more than one pair of hands.

What this layer adds is not another list of parcels. It is a different order. In a shipping overview parcels sit by date. In an operational dashboard what sits at the top is whatever deviates: what has stood still too long, what is coming back, what has damage, what nobody has picked up. The rest can stay quietly at the bottom, because there is nothing to do with it.

Context is kept alongside. A note at a parcel, a damage file with an amount and a deadline, a history you can search back over 24 hours, 7, 30, 90 or 365 days, and across everything built up inside the eighteen month retention period: that is what a team needs in order not to start over every morning. If you want to see exactly how the data arrives and what is and is not stored, that is on the how it works page and in the security explanation.

And the most important caveat is on every page of this product: this is an independent product from TheSEO and not software from MyParcel itself. There is no official affiliation, no partner status and no shared brand. MyParcel is the party you make your shipping arrangements with; we read the parcels out with your key and build the operation around them.

6MP.01 · workspaces in the product
4MP.02 · plans with their own limits
5MP.03 · minutes, the shortest sync interval
0MP.04 · labels we sell

MP.01 to MP.04 are properties of the product and the plans, not results and not usage figures. Source: features.json and prices.json.

WORK.MP01 · six workspaces

Six places, each answering one question.

The product is not one list with filters. It is six workspaces that each serve their own moment in the parcel cycle. Below is what is in each workspace and what you open it for.

01 workspace Announced

Announced, but not yet on its way

A parcel is announced the moment the label is created and the carrier is expecting the package. Between that moment and the first scan sits a gap where in practice most of the quiet problems begin: a package that was not handed over, a label that ended up on the wrong pile, a collection round that was skipped.

This workspace watches exactly that gap. Parcels announced longer than forty-eight hours ago without progress come to the top instead of sinking away. You filter on status, sort the list by what matters to you, and set which columns stay visible yourself, so your screen looks the way your operation works.

From the list you open the parcel detail with the full status history, and you search on the recipient when a client calls without an order number to hand. The question this workspace answers is short: what has stood still before the client notices?

Functions according to features.json: detection of forty-eight hours of delay, status filters, sorting, your own columns, parcel detail, searching on recipient.

FIG.MP03: Announced, sorted by standstillschematic example
workspace · announcedfictional data
everythingtodaylonger than 48 hoursown columns
#SG-1831Studio Groen · announced Thu 09:144 days still
#NL-2948Nordic Living · announced Fri 16:0251 hours still
#BP-7720Buitenpost · announced Mon 08:41normal
#SG-1846Studio Groen · announced Mon 10:07normal

The example is schematic, with fictional orders and shops. The bar shows how long a parcel has been announced without a first scan.

02 workspace Shipped

On its way, and what goes wrong on the way

As soon as a package has its first scan, it moves to Shipped. Here sits the tracking status of every parcel across all connected shops, with filters for delivered, in transit and delayed. You choose how far back you look: twenty-four hours, seven days, thirty, ninety, three hundred and sixty-five days, or everything.

The difference with an ordinary tracking page is in what you can put next to it. At every parcel you record a note, so the next colleague sees that the client has already been called and what was agreed. From the same row you start a damage file if the package arrived damaged, and you open the customs document if the parcel is going outside the EU.

Anyone who wants to process their figures elsewhere exports the selection as CSV. This is deliberately not a locked down report: it is your data, in a file every spreadsheet opens. The question here is: which parcel on its way is asking for a human?

The functions listed in features.json: tracking status, filters for delivered, in transit and delayed, history windows from 24 hours to everything, notes, damage claim, customs document, CSV export.

FIG.MP04: Shipped with notes at the parcelschematic example
workspace · shippedfictional data

History window

24 hours7 days30 days90 days365 dayseverything
#NL-2941delivered Tue 11:22 · no action neededdelivered
#SG-1829note: client called, waiting for a new delivery attemptdelayed
#BP-7702note: box dented, damage file createddamage
#NL-2955in transit · customs document attachedin transit
export: current selection as CSVcsv

Schematic example again, this time with fictional orders and notes. Notes are free text from your team, not something the system fills in.

03 workspace Returns

What comes back, recognised as coming back

A return is technically just another parcel, and that is exactly why returns make so much noise in an ordinary list. Without recognition a return label counts as a new outgoing parcel, the same order number appears two or three times, and nobody knows any more whether that package is going out or coming back.

This workspace recognises returns as returns and sets them apart. You filter on what is already in and what is still on its way, and per row you open the parcel detail with the full history, so you can see when the label was created and where the package is.

The practical effect is that your outgoing flow makes sense again. Your Announced and your Shipped are about packages going to clients, and returns have their own place with their own question: what is coming back, and is it in yet?

Functions according to features.json: return detection, filters for return received and in transit, parcel detail.

FIG.MP05: returns pulled out of the outgoing flowschematic example
workspace · returnsfictional data

Without return recognition

#SG-1831 · outgoingparcel
#SG-1831 · return label, counts as a new parcelnoise

With return recognition

#SG-1831return recognised and tied to the original parcelreturn in
#NL-2933return on its way to the warehousein transit
#BP-7688return in, parcel detail with the full historyreturn in

Also schematic, with fictional order numbers in it. It shows the difference in presentation, not a measurement of return rates.

04 workspace Online shops

The shops themselves, with the key, the limit and the styling

This is the administration part. You add online shops, change them or take them out, and per shop you record the MyParcel key the parcels are fetched with. How many shops you may connect depends on your plan, and that counter is simply in view, so you do not run into an unexpected limit.

Per shop you see its own figures, so you can compare without building a report first. Client communication sits here too: the sender, the colours and the content of the emails per online shop, a history of what has been sent, a daily digest and the option of a sender domain of your own.

One thing belongs here honestly. The renewed email chain around branding and client emails is still behind a release gate and is released only once the chain has been walked through end to end. The public gate register says the same thing, and we only take it off this page once it really holds.

From features.json, the functions here: adding, changing and removing a shop, MyParcel key, plan limit, figures per shop, branding, client email, email history, daily digest, own sender domain.

FIG.MP06: connected shops and the plan limitschematic example
workspace · online shopsfictional data
Nordic Livingkey active · digest on · own senderconnected
Studio Groenkey active · digest on · default senderconnected
Buitenpostkey active · digest offconnected
Kade Zevenkey not filled in yetwaiting for a key
Plan limit Growth: 12 of 80 online shops in use room left
release gate: renewed branding and client email chainstill closed

A schematic example with fictional shop names. The limit of 80 online shops belongs to the Growth plan and comes from prices.json.

05 workspace Damages

Files with a deadline that visibly runs

Damage is where money quietly leaks away. Not because nobody wants to pick it up, but because a damage report in an inbox has no deadline and a file in a spreadsheet has no owner. Carriers work to deadlines within which you have to report, and anyone who runs past them gets nothing back.

In this workspace you create a file from the parcel itself. The carrier deadline belongs to the file and its progress is visibly in view, so not as a date somewhere in a field but as something running while you watch. You record the amount, you move the status through the phases, and you write notes on what was agreed.

A drafted claim email already comes with it, so the report itself does not become a writing exercise, and you can search the history for older packages when a client raises it late. Important for your plan comparison: damage files are in the plan from Growth upwards, Starter does not have them.

Functions according to features.json: creating a file, the carrier deadline, a drafted claim email, the amount, the status progression, notes, visible deadline progress, searching historical parcels.

FIG.MP07: a damage file with a running deadlineschematic example
workspace · damages · filefictional data
SCH-0042#BP-7702 · Buitenpost · box dented on arrivalopen
Carrier deadline running deadline running
Amountthe damage amount recorded with the filefilled in
Claim emaildrafted from the file, a person sends itready
Note"photos received from the client, forwarded"team
status: reported · under review · decided · settledphase 2

Schematic once more, with a fictional damage file. The bar stands for deadline progress in the product; the length of a deadline differs per carrier and per situation.

06 workspace Analysis

The picture across the shops, plus the wallboard

The five preceding workspaces are about today. Analysis is about the pattern. You choose a period of thirty, sixty or ninety days and see the delivery rate in it, the average delivery time, the busiest day, the spread across the weekdays, the monthly volume and the main destinations.

The part used most is shop performance, because that makes visible what you never see in separate accounts: that one shop structurally delivers more slowly than the others, or that the peak at one shop falls on Monday and at another on Thursday. Which is exactly the kind of insight you only get when your shops sit in the same picture.

You can also put the picture full screen as a wallboard, for a screen in the warehouse or the office. No separate licence, no extra module: it is the same data, larger. And note the nature of these figures: they are your figures from your parcels, not a benchmark and not a promise from us.

In features.json these functions are named: a period of 30, 60 or 90 days, delivery rate, average delivery time, peak day, weekday chart, shop performance, monthly volume, main destinations. The wallboard is in features.json under the functions that apply everywhere.

FIG.MP08: weekday spread and shop performanceschematic example
workspace · analysis · 30 daysfictional data
30 days60 days90 dayswallboard
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Nordic Livingdelivery rate and average delivery time per shopshop performance
Studio Groensame measure, different patterndeviating
Destinationsthe main countries and regions in the periodtop

A schematic example with a fictional spread and shop names. It shows which fields exist, not the outcomes of a real operation.

FLOW.MP01 · the daily cycle

From connection to follow-up in four steps.

You keep your existing process at MyParcel. This layer changes nothing about how you ship; it changes what you see and what you do afterwards.

daily cyclefour steps · six seconds per step · and then again
STEP 01STEP 02STEP 03STEP 04
step
  • Connect your online shops
  • Fetch the parcels
  • Exceptions at the top
  • Follow up together
  • You put your shops under one organisation and record the MyParcel key per shop.
  • Parcels and statuses are fetched periodically, at an interval that belongs to your plan: from thirty minutes down to five minutes.
  • Standstill, returns and damages come to the top.
  • Notes, files and status stay with the parcel, so the next colleague does not start working it out again.
How to read this. Four cells, four steps, and the marker walks them round. After step four it starts again at step one, because this is a cycle and not a one-off installation. The full description per step is in the four cards below.

Connect your online shops

You put your shops under one organisation and record the MyParcel key per shop. The plan limit is visibly in view.

Fetch the parcels

Parcels and statuses are fetched periodically, at an interval that belongs to your plan: from thirty minutes down to five minutes.

Exceptions at the top

Standstill, returns and damages come to the top. The rest stays quietly at the bottom, because there is nothing to do with it today.

Follow up together

Notes, files and status stay with the parcel, so the next colleague does not start working it out again.

What happens exactly between steps two and three, which fields are stored and for how long, is written out on the how it works page. The underlying sources are machine readable: the route register, the function map and the status of the release gates sit as JSON in the document register, so you can read them yourself without taking us at our word.

See the full method →
LIMIT.MP01 · the boundary

What this product is expressly not.

A dashboard that promises everything does nothing well. So here are the boundaries, before you read on.

It sells no labels

Where you have to be for these things instead.

  • No shipping labels. Not a single label is created, no carrier is booked and no rate is negotiated.
  • No shipping platform. We are not an alternative to the party your shipping contract runs with.
  • No WMS. No stock, no order picking, no warehouse locations and no purchasing.
  • No official MyParcel software. Developed independently by TheSEO, without affiliation or partner status.
  • No replacement for your customer service system. Notes belong to the parcel, not to a ticket flow.

When you are better off choosing something else

Three situations in which we are honestly not the right choice.

  • You have one online shop with a quiet shipping flow. Then your existing MyParcel overview is enough and here you would be paying for air.
  • You want a grip on stock and order picking in the warehouse. Then you belong with a warehouse system, and we would rather say that now than after an invoice.
  • You are after cheaper shipping rates or a different carrier. That is a conversation with your shipping party, not with us.
The position in one sentence: this is the operational layer between a single shipping account and a full warehouse system. Anyone who wants labels goes to MyParcel. Anyone who wants stock goes to a WMS. Anyone who wants to know which parcel is asking for action today is in the right place here.
RATE.MP01 · current monthly prices

Four plans, with limits you can read up front.

The amounts come from the current Stripe products. The limits come from the production configuration. Both sit in the same machine readable register.

FIG.MP09: shop limit and sync interval per planplan properties
plan ladder · online shops and synchronisationsource prices.json
Starter40 online shopssync 30 min
Growth80 online shopssync 15 min
Pro250 online shopssync 10 min
Enterpriseunlimited, technical ceiling 9,999sync 5 min
damage files: available from Growth upwards, not in Starterplan difference

Properties of the plans, not results. The bars are in proportion to the highest limit and are a rendering, not a measurement.

Price source: Stripe live mode · verified 2026-07-28 · automatic payment is deliberately still off until the release gates are green. The exact total and the VAT treatment are confirmed in Checkout before payment. Full explanation on the pricing page.

NEXT.MP01 · three steps

Look first, then make it fit, and only then pay.

The order is fixed and is the same on every page of this product. Step three is deliberately still closed.

step 01 · free

The public preview

The full interface with fictional sample data, without an account and without a sales conversation first. All six workspaces, plus parcel detail, search and the wallboard. Nothing is sent to production.

Open the preview →
step 02 · a conversation

The plan check

We look together at your shops, your volume and the question of whether this product earns you anything. If it does not fit, we say so. That is not politeness but self-interest: a client in the wrong place leaves anyway.

Start the plan check →
step 03 · still closed

The payment route

Automatic payment is off until every release gate is green: the VAT treatment, idempotent handling of payment events, tenant isolation, the client portal and a successful test payment from end to end.

waiting on release gates

Why that third step is closed you can read rather than assume. The status of every gate is in the public gate register, and what sits behind it is explained on the security page. We name no date on which the button opens, because that date depends on the gates and not on our planning.

HONEST.MP01 · expectations

What you will and will not hear from us.

This list is not here for show. Everything on the left can be read back or checked; everything on the right we deliberately do not promise.

You may hold us to this

Five things that can be checked.

  • It runs in production every day, with real parcels, and not only as a demo. That is the evidence we have, and it says so in our software overview too.
  • The full preview is public, without an account, with fictional sample data: the interface you see is the interface.
  • Prices come from Stripe and the plan limits from the production configuration, with the verification date visible on the page.
  • Automatic payment is off until the gates are green, and which gates are open can be read publicly.
  • Monthly cancellation is the public starting position, unless an agreement signed by both parties says otherwise.

This we do not promise

Six things you will never read here.

  • No delivery figures, savings amounts or hours saved per week. We do not measure your operation, so we have no figure about it.
  • No client counts and no names of users, as long as nobody has said that is allowed.
  • No promise that client questions disappear. They become answerable sooner, which is something else.
  • No labels, no shipping rates, no stock and no warehouse functions.
  • No official MyParcel software, no partner status and no shared brand.
  • No date on which the payment route opens, because that depends on the gates and not on a planning schedule.
FAQ.MP01 · frequently asked questions

The questions that come back nearly every time.

Nine questions about the boundary, the plans and the status of the payment route.

Is MyParcel Dashboard official MyParcel software?

No. MyParcel Dashboard is developed independently by TheSEO and has no official affiliation with MyParcel. MyParcel stays the party where you arrange your shipping contract, your labels and your carriers. This dashboard reads out the parcels of your connected online shops and lays an operational layer over them.

MyParcel already supports several online shops itself. So what does this add?

That is right, and we always say so. The difference is not in connecting shops but in what you do with the parcels afterwards. This layer puts exceptions at the top instead of every parcel by date, keeps notes and follow-up with the parcel, keeps damage files with the carrier deadline in them, and shows analysis across all shops instead of per shop separately.

Does the dashboard create shipping labels?

No. Not a single label is created, no rate is negotiated and no carrier is booked. That stays entirely with MyParcel and your carriers. This is a reading layer with follow-up on top, not a shipping platform.

Is this a WMS or a stock system?

No. There is no stock management, no order picking and no warehouse layout in it. If that is what you are after, you belong with a warehouse system and not with us. This layer starts the moment a parcel is announced and stops once the file around it is closed.

How often are the parcels fetched?

The synchronisation interval depends on your plan: 30 minutes on Starter, 15 minutes on Growth, 10 minutes on Pro and 5 minutes on Enterprise. Those intervals come from the production configuration and are also in the machine readable price register.

How many online shops can I connect?

Starter sits at 40 online shops, Growth at 80, Pro at 250 and Enterprise at unlimited, with a technical ceiling of 9,999. Those limits are hard: they sit that way in the application configuration and in the price register.

Are damage files in every plan?

No. Damage files are in the plan from Growth upwards and Starter does not have them. That is a plan property from the same configuration as the shop limits and the synchronisation intervals.

Can I look at the product without an account?

Yes. The platform preview is public and asks for no account. You click through all six workspaces, the parcel detail, the search function and the wallboard. Everything you see there is fictional sample data and nothing is sent to production.

Can I pay now and start straight away?

No, and that is a deliberate choice. The automatic payment route is off until the release gates are green, among them the VAT treatment, idempotent handling of payment events, tenant isolation, the client portal and a successful test payment from end to end. Until then the start runs through a plan check in which we first look at whether your situation fits.

LINK.MP01 · further reading

Where to look after this. The deeper MyParcel product pages are still Dutch only and each is marked NL.

The rest of this product, and the work we do around it. Having the online shop itself built or rebuilt runs through our work as a WordPress specialist.

How it worksThe data flow step by step, plus the system boundaries per workspace. Pricing and limitsFour plans side by side, the VAT explanation and the status of the payment route. Security and privacyTenant isolation, key management, the processor role and the open release gates. Document registerEvery human and machine readable source behind this product in one place. Getting startedThe plan check and the route for existing users of the dashboard. Platform previewThe real interface with fictional sample data, without an account. SEO for online shopsThe growth side: findability, category structure and the technical work. Online shop analysisHow to examine an online shop before you start turning the dials. Software from TheSEOThe instruments we build ourselves and use ourselves every day. JarvisOur other product: one shared company brain for your people and your AI. AI and automationWhat we do and do not do with AI, and where the human control sits. ContactA question that is not answered here you simply ask us directly.
NEXT.MP02 · starting under control

Look around first. Talk afterwards.

The preview is public and asks nothing of you. If you like what you see, in the plan check we look together at whether your shops, your volume and your way of working benefit from this. An independent product from TheSEO, not software from MyParcel itself.

Open the platform preview →

Back to the short version