Have you ever placed an order on time and still had it arrive late? The cause is almost never that you did something wrong. More often, the system calculating the pickup date is using a generic rule instead of the carrier's or distributor's real calendar. That gap, small as it looks, is what makes you look bad to a customer when it isn't your fault at all.
That's exactly what happened to a group of pharmacies that uses its own platform to decide when to close each order to its distributor.
What was actually happening
The screen where staff decided whether to close the order now or wait calculated the pickup with a simple rule: close before noon and pickup was that same afternoon; close after noon and pickup was the next day. It seemed reasonable, and for months nobody questioned it, because most days it was right.
The problem is the real carrier doesn't work that way. It picks up on specific days and at specific times depending on the day of the week, and Fridays cut off much earlier than the rest. And, above all, it doesn't pick up at all on weekends. The screen, however, could still offer Saturday or Sunday as if they were just another pickup slot, because the generic rule had no idea those days didn't exist for the carrier.
The result: someone closed an order trusting the date on screen, and that order didn't go out when it should have. Not because anyone ordered it wrong, but because the date they'd been promised wasn't real.
How do you spot a pickup date that isn't real?
Your system doesn't need to "break" for this to happen to you. The signal is subtler: the date it gives you looks reasonable, it matches what you'd expect, and the order still doesn't arrive when it should. Three quick questions to check this in your own business:
- Does the date your system offers change depending on the day of the week, or is it always "the next available pickup," calculated the same way every day?
- Has it ever offered you a public holiday, a Saturday or a Sunday as a delivery date, when you know that particular supplier doesn't work those days?
- If you confirm the order right as the chosen pickup window is about to close, does the system warn you that slot no longer holds, or does it let you carry on as if nothing happened?
If you can't answer one of these, you've probably never checked it against your supplier's real calendar, only against what "seemed logical" when it was built.
What happens when you order from several suppliers with different calendars?
It gets more complicated when it isn't just one carrier, but several suppliers, each with its own cutoff days, holidays and exceptions. A single generic rule can get it right with one and fail systematically with another, and nobody notices because each late order gets explained away, one by one, as a one-off: "the carrier was running late this time," "the holiday caught us out this time." Only by looking across several months together does the pattern show up: these aren't one-off cases, it's the same rule failing in the same place every time.
The pharmacy group's fix wasn't to make the rule "a bit smarter." It was to stop inventing a date and start representing the carrier's actual calendar, day by day, inside the system itself. The screen no longer calculates "before or after noon": it shows the next two pickups that will genuinely happen, each with its exact cutoff time. And if someone takes a while to confirm the order and the chosen pickup stops being valid while they decide, the system corrects it on its own instead of letting the deadline pass unnoticed.
This was tested against the exact edges of every cutoff: one minute before the deadline and one minute after, for every day of the week. It isn't a reasonable approximation; it's the real calendar, checked to the minute.
The decision rule
Even if your business has nothing to do with pharmacies, the rule carries over entirely: if you coordinate orders with a supplier, distributor or carrier that has its own fixed calendar, a generic "before or after a certain time" rule isn't enough. Your system needs to know THAT calendar, exceptions included, or sooner or later it will promise someone a date that doesn't exist.
What to check this week
You don't need to build anything new to start checking this:
- Pull the last 10 orders that arrived late from a supplier, or that you delivered late to a customer, and check whether the "promised" date fell on a day or time when there genuinely was no pickup or delivery.
- Ask the carrier or supplier directly for their exact calendar (days, cutoff times, holiday exceptions) and compare it with what your system, spreadsheet or team habit assumes.
- If what you use to decide when to order is a rough, "by eye" approximation, write it down: it's the fastest way to see where it diverges from reality.
If you run a pharmacy chain, you can see what a group of pharmacies can ask its own data on a platform like this one. This kind of detail is part of the same thing that lets the group in this story see stock and sales across all its locations in one place and decide what to order, from whom, and when, without relying on someone remembering each supplier's calendar by hand.
If you run several locations and coordinate orders with more than one supplier, it's worth checking whether your own system actually knows their calendars, or is just assuming them. Tell us about your case and we'll go through it together with your data.