One MyParcel dashboard for several online shops.

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.

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.

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.

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.