Switching 3PL Providers in Europe: A Pre-Migration Checklist for DTC Brands
15.07.2026
Amazon Ends FBA Commingling Across Europe: The FNSKU-on-Every-Unit Rule Resellers Must Now Follow
21.07.2026
FLEX. Logistics
We provide logistics services to online retailers in Europe: Amazon FBA prep, processing FBA removal orders, forwarding to Fulfillment Centers - both FBA and Vendor shipments.
A seller-fulfilled Amazon Business offer looks fine in Seller Central on a Tuesday. Orders are shipping, tracking is uploading, nothing looks broken. Then a performance notification arrives referencing a Business Hour Delivery Rate threshold, and the seller realizes they have never actually measured that number against business-hour expectations rather than standard delivery promises. This distinction matters because Amazon Business buyers often order against tighter delivery windows than typical retail customers, and FBM sellers who fulfill against consumer-style carrier schedules can quietly fall short without any single shipment looking late in isolation. The practical question is not whether packages arrived, but whether they arrived inside the business-hour window Amazon is now measuring against a 90% threshold, with a compliance checkpoint referenced for September 30. This affects self-ship (FBM) offers specifically, not FBA-fulfilled listings, and it changes how sellers should plan carrier selection, cutoff times, and delivery-performance monitoring across UK, DE, and other EU marketplace accounts.
What the Business Hour Delivery Rate actually measures
Business Hour Delivery Rate is a performance metric tracking how often seller-fulfilled orders arrive within the delivery window Amazon Business associates with standard business operating hours, rather than a generic day-based delivery estimate. For self-ship Amazon Business compliance, this reframes the delivery clock: a parcel that arrives at 7pm on the promised date may still count against the rate if the buyer's business-hour expectation closed earlier. The mechanism is separate from general FBM delivery performance EU metrics sellers may already track, because it is scoped specifically to Business orders rather than the full order mix.
Sellers who fulfill Amazon Business and standard consumer orders through the same carrier account often assume their existing on-time rate covers this. It typically does not, because the underlying measurement window differs. A carrier scan showing delivery on the correct calendar day is not the same as a scan showing delivery inside the business-hour cutoff Amazon Business tracks. Until a seller pulls the actual Business Hour Delivery Rate report, the gap between assumed performance and measured performance is invisible.
What sellers need to confirm before September 30
The first control point is whether the seller can even see a Business Hour Delivery Rate figure in performance reporting, separate from general late-shipment or delivery-rate metrics. Some FBM sellers only monitor Order Defect Rate and standard delivery estimates, which do not surface this business-hour breakdown on their own. Confirming visibility into the actual metric is the starting point, not an assumption that existing dashboards already show it.
The second confirmation is which carrier services are being used for Amazon Business orders specifically. A carrier product with a next-day-by-end-of-day promise is structurally different from one with a defined business-hour delivery commitment, and mixing the two under one fulfillment template can quietly drag the rate down even when overall on-time performance looks acceptable.
What happens when responsibility for this is unclear
When no one owns monitoring this metric, the first sign of a problem is often a performance notification rather than a gradual warning trend, because the underlying data was never being reviewed proactively. By the time the notification lands, several weeks of order volume may already be reflected in the rate, making a quick recovery harder inside a single reporting cycle.
The operational risk tied to seller-fulfilled Amazon Business offers falling short of the threshold is reduced marketplace eligibility for those specific offers, which is a different consequence than a generic account health warning. A seller who assumes standard FBM delivery performance EU tracking is enough may not realize the Business offer itself is exposed until visibility or eligibility narrows for Business buyers specifically.
Where responsibility actually sits in a self-ship setup
In most FBM operations, three parties touch this outcome: the seller who sets the fulfillment template and cutoff logic, the carrier who executes the actual delivery window, and Amazon, which measures the outcome against the Business Hour Delivery Rate threshold without adjusting for carrier-level nuance. The seller is the only party positioned to reconcile these three views before a shortfall becomes visible externally.
This is where an e-commerce fulfillment service model changes the picture, not because a third party absorbs legal responsibility, but because a dedicated operational layer can monitor carrier-level delivery scans against business-hour windows continuously, rather than sellers discovering a gap only after a performance notification. Sellers running Amazon Business FBM offers across UK, DE, and other EU stores are effectively running parallel delivery-window logic per marketplace, and treating all Business orders as one undifferentiated FBM stream is often the point where the metric starts slipping without an obvious single cause.
Data to confirm first
- Whether Business Hour Delivery Rate appears as a distinct line in current performance reporting.
- Which carrier service level is mapped to each Amazon Business fulfillment template.
- Whether cutoff times reflect the carrier's actual collection schedule, not an assumed one.
- Whether tracking uploads are timed correctly relative to dispatch, since delayed uploads can distort measured performance.
Workflow checks per marketplace
- Confirm delivery-window expectations separately for UK, DE, and other EU Amazon Business stores, since carrier networks differ by country.
- Check whether the same self-ship Amazon Business compliance logic is applied consistently across marketplaces, or copied from one store to another without adjustment.
- Review whether high-volume order days shift carrier collection times enough to affect business-hour arrival.
- Identify whether any SKUs are consistently tied to late-arriving carrier lanes.
Cost and exposure checks
- Estimate how many current Amazon Business orders would fail a stricter business-hour cutoff if carrier performance stayed unchanged.
- Check whether existing carrier contracts include a business-hour delivery product, or only standard next-day options.
- Confirm whether switching carrier tiers for Business orders changes per-order cost meaningfully.
- Flag any marketplace where FBM delivery performance EU figures already show a downward trend.
Ownership and escalation checks
- Assign a named owner for reviewing Business Hour Delivery Rate reporting on a recurring basis, not only after a notification.
- Define who decides whether to re-route Amazon Business orders to a faster carrier lane if the rate drifts downward.
- Confirm who is authorized to change fulfillment templates or cutoff settings per marketplace.
- Set a review point before September 30 rather than treating it as a single deadline check.
Deciding what to fix first if the number looks weak
If a seller pulls the Business Hour Delivery Rate and it sits meaningfully below 90%, the fix is rarely one thing. The decision rule is to separate carrier-level delay from template-level cutoff error before choosing an action. A carrier consistently scanning deliveries after the business-hour window points to a service-level mismatch; a fulfillment template with a cutoff time later than the carrier's actual collection slot points to a configuration error the seller can fix without changing carriers at all.
Sellers running high Business order volume across multiple EU stores often find the fastest correction is marketplace-specific: fixing the UK cutoff logic does not automatically fix DE, because collection schedules and carrier networks differ. Where volume or SKU complexity makes manual monitoring unreliable, this is the point where a seller weighs bringing in operational support that already separates delivery-window performance by marketplace and carrier lane, rather than trying to reconstruct that view internally under deadline pressure.
Owner
The seller's fulfillment operations lead should hold responsibility for reviewing Business Hour Delivery Rate reporting per marketplace, since carrier performance and cutoff logic differ by store and no external party can see this without seller-level Seller Central access.
Data checkpoint
Confirm the tracking-upload timestamp against actual dispatch time weekly. A delayed upload can make an on-time delivery appear late in reporting, distorting the measured rate without any real carrier failure.
Escalation rule
If the rate drops two reporting cycles in a row, escalate to a carrier or template review immediately rather than waiting for a formal notification, since notifications typically reflect several weeks of already-accumulated shortfall.
What to lock down before the next reporting cycle
The practical decision here is not whether to react to a notification, but whether current FBM operations already separate Amazon Business orders from standard consumer orders at the carrier and cutoff level. Sellers who can answer that question with confidence are in a stronger position than those relying on an overall FBM delivery performance EU figure that blends both order types together.
Before the September 30 checkpoint, confirm visibility into the actual Business Hour Delivery Rate metric, verify carrier service mapping per marketplace, and assign a named owner to the recurring review. None of this requires guessing at Amazon's exact policy language; it requires seeing the seller's own delivery data clearly enough to know where the gap sits, if one exists.
Sellers uncertain whether their current self-ship setup can sustain this threshold across UK, DE, and other EU stores should treat this as an operational review, not a compliance panic, and check the underlying carrier and cutoff logic before assuming a fix is needed at all.
Compliance obligations under Amazon Business policy should be verified directly against Amazon's own seller communications and terms, since thresholds and enforcement details can be updated without notice. For the operational side, FLEX. supports sellers who need a clearer view of carrier performance, cutoff logic, and marketplace-specific fulfillment routing as part of a broader e-commerce fulfillment service setup. If self-ship delivery performance across EU Amazon Business stores needs a second look before the next reporting cycle, that review is a reasonable next step to plan now rather than after a notification arrives.
