Warehouse Staffing in France: What the 35-Hour Work Week Means for Peak-Season Scheduling
18.08.2026
Protecting Store Conversion in France: How Carrier Cut-Off Rules Guard Customer Delivery Promises
18.08.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 merchant shipping domestically within France finalises next month's shipping-cost sheet on the 3rd, using the surcharge figure they remember from last time. Three weeks later, the invoice lands with a different number, and the margin on that batch of orders is already gone. The mechanism behind this is simple: DPD's fuel surcharge is not a fixed line item, it moves monthly, and road and air components do not always publish on the same schedule. In August 2026, DPD France's confirmed road surcharge sat at 20.5%, while the air-freight figure was still pending on the same page. This checklist gives merchants a repeatable way to check the current figure, apply the right component to the right shipment type, and build in a buffer for the days when the published number isn't final yet.
Why the DPD surcharge behaves like a moving cost, not a fixed one
Fuel surcharges attached to carrier contracts are recalculated on a rolling basis, usually tied to an external fuel-price index rather than a value the carrier sets once and leaves alone. That means the percentage a merchant applies to a shipment in June may already be wrong by August, even if nothing in the merchant's own shipping profile has changed. Treating the surcharge as a fixed cost line inside a spreadsheet is a common, avoidable planning error, and it tends to surface only when someone reconciles invoiced freight cost against the projected number.
The complication merchants often miss: road and air surcharges are published as separate line items, and they don't always update in sync. A merchant checking DPD's surcharge page mid-month may see the road figure confirmed while the air component still shows a placeholder or a prior-month value. Building an FBA carrier service France cost model around whichever number happens to be visible that day, without checking which component actually applies to the shipment, is where the error compounds.
What to confirm before locking a cost projection
Before finalising a monthly shipping-cost sheet, confirm two separate things: which surcharge component applies to the shipment type being costed, and whether that specific component is marked as confirmed or pending on DPD's live page. A parcel moving by road carries the road surcharge; anything routed through an air network carries the air component, and the two are not interchangeable in a cost model even when a merchant ships both.
Check the live page directly rather than pulling from a saved bookmark result, an old invoice, or a number a colleague mentioned last week. DPD updates the page on a rolling monthly basis, and a cached screenshot from two months ago carries no weight once the new figure is published.
What breaks when the wrong figure gets used
When a merchant applies a stale or incomplete surcharge figure, the cost-per-shipment projection drifts from the actual invoiced amount, and that drift shows up as either under-quoted shipping fees passed to customers or an unexplained margin gap discovered at month-end reconciliation. Neither is a small correction; both require someone to go back through a month of orders and figure out where the assumption broke.
The air-freight gap is the sharper risk. If a merchant assumes the air component matches the road figure because that's the only number visible, and the air surcharge later publishes higher, every air-routed shipment that month was under-costed without anyone noticing until the invoice arrived.
Building a monthly audit habit instead of a one-time check
The fix here isn't a smarter spreadsheet formula, it's a habit: check DPD's surcharge page as a fixed step in the monthly cost cycle, not as a one-off task done whenever someone remembers. A merchant running domestic France shipments should treat this the same way they'd treat checking a carrier rate card before quoting a new SKU — a recurring control point, not a background assumption.
Set the check to happen on the same date each month, ideally a few days before shipping-cost projections get locked for the coming cycle. If the road figure is confirmed but the air component is still pending at that check-in, don't wait for it — apply a buffer to the air-routed portion of the cost model and revisit once the figure publishes. This is the same logic FLEX. applies internally when tracking DPD France surcharge monthly tracking data across client shipment volumes: check early, flag what's unconfirmed, and never let a pending figure sit unflagged in a live cost model.
Monthly check — road surcharge
- Open DPD's live surcharge page directly, not a saved link or prior screenshot.
- Confirm the current month's road percentage is marked final, not provisional.
- Apply the road figure only to shipments actually routed by road.
- Log the confirmed percentage and the date it was checked.
- Compare against the prior month's figure to flag unusually large swings before applying it.
Monthly check — air-freight component
- Check whether the air surcharge is published alongside the road figure or still pending.
- If pending, note the last confirmed air figure separately from the current road number.
- Never apply the road percentage to air-routed volume as a substitute.
- Set a follow-up check for later in the month if the air component wasn't ready at first review.
- Flag any shipment quoted before the air figure confirmed for later reconciliation.
Cost-model buffer controls
- Add a small percentage buffer to air-routed cost lines when that component is unconfirmed at planning time.
- Avoid rounding the buffer down just to hit a target margin on paper.
- Document why the buffer was applied, so it can be removed once the real figure publishes.
- Review buffered lines against the final invoice once the month closes.
- Adjust the buffer size over time based on how often the air figure has lagged the road figure historically.
Ownership and review cadence
- Assign one person or team as the owner of the monthly surcharge check, not a shared, undefined task.
- Set the check date to a fixed day in the monthly cost cycle, not a floating reminder.
- Require sign-off before shipping-cost projections are finalised for the month.
- Escalate to whoever manages carrier-cost tracking if a figure is still unpublished close to the cut-off.
- Keep a running log of confirmed monthly figures for trend visibility across the year.
Turning the check into a repeatable operating rule
The decision rule is straightforward: never finalise a shipping-cost projection using a surcharge figure that hasn't been confirmed on DPD's own page within the current planning window. If the road figure is confirmed and the air figure is pending, split the cost model — lock the road-based lines, buffer the air-based lines, and revisit before invoices land. This keeps a single unconfirmed component from distorting an entire month's cost projection.
For merchants running higher shipment volumes, this check stops being a five-minute task and starts looking like an ongoing carrier-cost monitoring function — something that needs a fixed owner, a fixed cadence, and a clear escalation path when a figure doesn't publish on time. That's a workload most small teams don't budget for until the first reconciliation gap forces the conversation.
Owner
Assign one person to check DPD's surcharge page monthly. Without a named owner, the check gets skipped whenever the usual person is busy, and the stale-figure risk returns.
Checkpoint
Confirm road and air components separately before locking cost projections. Treat each as its own data point with its own confirmation status, not one combined number.
Escalation
If a figure is still pending close to the planning cut-off, escalate rather than guess. Apply a documented buffer and revisit once DPD publishes the final number.
Deciding whether this check needs a dedicated owner
The core decision for most merchants isn't whether to check the surcharge page — it's whether checking it monthly, splitting road from air, and buffering unconfirmed figures is something they can sustain internally as shipment volume grows. For a handful of domestic France shipments a month, a spreadsheet reminder might hold up. Once volumes climb, or once a merchant is running mixed road and air routing alongside broader forwarding to Amazon Europe or pre-Amazon storage needs, the surcharge check becomes one more moving part in a cost model that already has several.
The figure itself will keep changing — August's 20.5% road surcharge is a snapshot, not a baseline, and it should be re-verified directly on DPD's page before anyone uses it in a live projection. What doesn't change is the discipline required to catch the gap before an invoice does.
Merchants running domestic France shipping alongside broader fulfilment work — storage, returns, or forwarding into Amazon's network — don't always have spare capacity to own a monthly carrier-surcharge audit on top of everything else. FLEX. builds this kind of carrier-cost tracking into its French fulfilment support, monitoring DPD's road and air figures as part of the wider cost-to-serve picture rather than leaving it as a separate task someone has to remember. If shipping-cost projections have drifted from invoiced totals more than once this year, that's usually a sign the monthly check needs a fixed owner. Get in touch with FLEX. to talk through where that owner should sit.
