dpd prestashop: which shipping setup should you choose?
A DPD storefront module can fit one PrestaShop store and one shipping point. A shipping platform brings carrier labels together. An OMS/WMS becomes useful when channels, warehouses, or routing rules multiply. In every case, accept the flow with one home order, one Pickup order, both labels, and tracking back in PrestaShop.
By Diogo Monteiro · E-commerce Integration Expert· Updated September 24, 2026· 4 min readThe essentials
- A storefront module is the lightest route for one PrestaShop store shipping from one location; a shipping platform brings several carriers into one label workspace.
- Start with the DPD region and contract account. A label from the wrong account or method is not a successful test.
- The paid order, service, Pickup code, label, tracking number, and shipped status must agree from end to end.
- An OMS/WMS earns its place when several channels, warehouses, or repeated routing rules need one operating queue.
At 5:20 p.m., the final DPD parcel is ready. The label prints, yet the PrestaShop order still shows the wrong delivery method and no tracking number. A DPD PrestaShop flow is not accepted when paper leaves the printer. The paid order, service, Pickup code, label, tracking number, and shipped status must agree from end to end.
DPD PrestaShop: three setups for three operating models
A storefront module is the lightest route for one PrestaShop store shipping from one location. It keeps the order and carrier actions close to the shop. It is enough only if it preserves the paid delivery method, the Pickup selection, and the return of tracking.
A shipping platform brings several carriers into one label workspace. It suits an operation where stock and order preparation are already controlled elsewhere and the main need is shared carrier execution.
An OMS/WMS becomes relevant when orders arrive from several channels, stock sits in several warehouses, or routing rules must be applied consistently before packing.
| Setup | Good fit | Acceptance point |
|---|---|---|
| Storefront module | One store, one shipping point | Method, Pickup, label, tracking |
| Shipping platform | Several carriers, simple fulfillment | Order source and status return |
| OMS/WMS | Several channels or warehouses | One rule set across the operation |
Whichever route you assess, start with the DPD region and contract account. The reviewed myFulfillment adapter is for DPD France and keeps separate account values for Classic, Predict, Europe, and Relais. A label from the wrong account or method is not a successful test. DPD France also documents two integration routes: a file into Station DPD or webservice labeling and tracking (DPD France, 2026).
The failures sit at the handoffs, not at the printer
First, the paid PrestaShop delivery method can map to the wrong DPD service. Second, a Pickup order can lose the selected point code before label creation. With myFulfillment, the optional Boostmyshop module passes that code from PrestaShop for DPD France; check the value, not only the town name.
Pickup points account for a substantial share of deliveries. Fevad’s 2026 key figures report EUR 196.4 billion and 3.2 billion French e-commerce transactions in 2025, with out-of-home delivery close to one order in two. Arcep and CREDOC’s 2026 study found that nearly four recipients in ten prefer pickup points and 62% experienced at least one delivery problem in six months, including missing tracking information.
The third failure is the return path. DPD creates the label and tracking number, but PrestaShop receives neither the mapped shipped status nor the same tracking reference. Arcep counted 1.7 billion parcels in 2024, up 3.7% in its observatory published in 2025. That volume makes silent exceptions an operational concern. A 2024 review by Janinhoff and colleagues explains the operating value of pickup networks: parcel shops and lockers consolidate recipients at one location and reduce failed attempts.
PrestaShopPaid order
DPDLabel and trackingOne anonymized home-and-garden retailer used PrestaShop among five sales channels. Its order team moved from 3 to 5 platform tabs to one screen, while shipments moved from 1 to 2 days late to same-day. These are that retailer’s order-operation results, not DPD performance figures.
Run the DPD PrestaShop acceptance test in 20 minutes
Create two paid test orders: one home-delivery order and one Pickup order. During the first five minutes, verify that both arrive with the same references, addresses, items, payment state, and delivery methods. On the Pickup order, compare the selected point code with the value available for shipment.
Use the next five minutes for labels. The home order must call the intended DPD service. The Relais shipment must use the correct regional account, and its label must carry the chosen pickup point. Check the printer format as well as the readable address.
Spend the final ten minutes creating both shipments, then return to PrestaShop. Each order must show the configured shipped status and the same tracking number held by the DPD shipment.
- 1PrestaShop orderOrder number and delivery method presentCheck in PrestaShop
- 2Parcel checkItems and quantities validatedCheck at the packing station
- 3DPD shipmentLabel and tracking number createdCheck in the DPD account
- 4Tracking sync back to PrestaShopOrder marked as fulfilledCheck in PrestaShop
The first mismatch points to the setting that needs attention: import settings for missing order data, method mapping for the wrong service, pickup transmission for a missing point code, DPD account configuration for a rejected label, or shipping confirmation for absent status and tracking. Fix that handoff and repeat both orders.
Choose an OMS/WMS when several channels share the same rules
Keep the storefront module if it passes the test and one team controls one shop and shipping point. Keep a shipping platform if your only missing capability is a shared carrier-label workflow.
myFulfillment becomes useful when several channels need one order queue, several warehouses need routing, or the same carrier rule is being rebuilt in different shops. PrestaShop orders are imported through Webservices; after preparation, shipping confirmation can write the configured status and tracking reference back to PrestaShop. The DPD France adapter then handles the chosen account, method, label, and tracking events.
Use the PrestaShop integration and DPD integration pages for the supported mechanics. If Shopify is also in scope, the Shopify × DPD decision applies the same acceptance logic to that storefront.
Frequently asked questions
Use a storefront module for one shop and shipping point, a shipping platform for a shared carrier workspace, and an OMS/WMS when channels, warehouses, or routing rules need one operating queue.
Yes, when the selected pickup-point code survives from checkout to the DPD Relais label. With myFulfillment, the optional Boostmyshop module passes that code from PrestaShop.
After shipment creation, PrestaShop should receive the configured shipped status and the same tracking reference held by the DPD shipment. A printed label alone does not prove this return path.
DPD services and credentials are regional and contractual. Confirm the DPD country, centre, and account enabled for Classic, Predict, Europe, or Relais before testing labels.
Continue exploring
Stock availability, picking accuracy, and shipping times affect marketplace sales. Jonathan Coloma, COO of Repiauto, explains how his team went from 300 to 1,000 orders a day in two years. He describes the limits of paper-based work, ERPs built for different needs, a go-live estimate of fifteen days, and changes to his daily routine.
To hold up under peak volume, split the order queue into waves based on real operating constraints, then decide where barcode checks belong. At the packing bench, the operator verifies the parcel. Carrier rules select the service and print the label, so the next order can start without another decision.
Industrializing your purchasing means ordering on rules, not guesswork: at the right time (the reorder point), in the right quantity (your coverage period), from the right supplier, with a purchase order validated in one click. Available on replay.
See it in your own operations
Book a 20-minute call. We'll map your workflow and point out where it breaks. No slides.
Free 20-min call · No commitment