PrestaShop Dropshipping: Build a Reliable Order Workflow
A reliable PrestaShop dropshipping workflow connects a customer order to a supplier's acceptance, shipment and tracking information. Importing products into the catalogue completes only the first part of that process.
Start with one supplier and a small approved product range. This guide follows one order from payment review to delivery, including the points where someone must act when the supplier cannot fulfil it.
The workflow can begin with controlled manual handoffs and later use a connector. The operational states below are a suggested tracking model, not a list of built-in PrestaShop statuses.
1. Choose a Small Launch Scope
Define which supplier, products and delivery destinations belong in the first release. Exclude products with unresolved identifiers, unclear stock meaning or untested shipping arrangements.
Use the supplier qualification checklist before activating the range. Keep the approval record with the person responsible for buying and fulfilment.
Assign four responsibilities: catalogue accuracy, supplier submission, exception handling and customer communication. One person may cover several roles in a small shop, but each task needs an owner and a backup.
Write the service target for a new order. For example: “Every eligible paid order is reviewed and submitted during the next scheduled processing window, then checked for supplier acceptance.” Replace that example with a schedule your team can actually maintain.
2. Map Every Product and Variant
Create a mapping sheet with your product reference, any combination reference, supplier reference and the fulfilment route. Test the mapping against a sample order rather than matching products by similar names.
PrestaShop's product documentation describes supplier associations and supplier references. Treat those fields as catalogue information; the order handoff still needs a defined manual process or a verified integration.
| Your reference | Supplier reference | Variant | Route |
|---|---|---|---|
| DESK-TRAY-BLK | SUP-481-B | Black tray | Supplier A domestic |
| DESK-TRAY-WHT | SUP-481-W | White tray | Supplier A domestic |
| NOTE-A5 | SUP-722 | Plain notebook | Supplier A domestic |
Store the units explicitly. A supplier reference for a carton of ten is not interchangeable with your reference for one item.
Mark discontinued or ambiguous mappings as unavailable for new orders until resolved. Reusing an old reference for a different variant can turn an apparently successful handoff into a wrong-item shipment.
3. Define the Order States You Need to Observe
Use a simple operational tracker until your installed tools can represent the same facts. Keep it linked to the PrestaShop order reference and, when necessary, the individual order line.
| Operational state | Evidence required | Next owner |
|---|---|---|
| Ready for review | Order and payment checks completed | Shop operations |
| Submitted | Recorded submission identifier and time | Shop operations |
| Accepted | Supplier confirms quantities and references | Supplier fulfilment |
| Exception | Rejection, missing acknowledgement or changed terms | Shop support |
| Dispatched | Confirmed parcel and carrier information | Shop operations |
| Delivered or resolved | Delivery evidence or recorded resolution | Shop support |
Do not mark an order dispatched merely because the supplier received it. Acceptance and physical dispatch answer different questions.
If one order contains several supplier groups, track their progress separately. Follow the mixed-cart guide before using an order-wide label that may hide an unshipped line.
4. Prepare a Complete Supplier Handoff
Agree the minimum information the supplier needs to fulfil the order. Include your order reference, stable line reference, exact supplier SKU, quantity, delivery service and required delivery details.
Send customer information only through the agreed channel and only to the extent necessary for the fulfilment task. Avoid scattering copies across personal inboxes and uncontrolled spreadsheets.
For a manual pilot, maintain a submission register. For a connector, ask the provider to demonstrate how it records submission, retries and supplier acknowledgements for your installed versions.
Include a stable reference that the supplier can recognise when a submission is repeated. The expected result of a retry is one supplier order, not two parcels charged to your account.
If a submission times out, first check whether the supplier received it. Treat “no response” as unknown, rather than assuming the operation failed and immediately submitting a second unrelated order.
5. Require an Acceptance Result for Every Line
Set a deadline for acknowledgement based on the supplier agreement and your customer promise. Create an exception task when that deadline passes.
An acceptance should identify the references and quantities the supplier has reserved. A generic “file received” message does not demonstrate that the products are available.
Example: the customer orders two black trays and one notebook. The supplier accepts one tray and the notebook. Your tracker must show the missing tray rather than marking the whole order accepted.
Give support a defined next step: ask the customer about an available alternative or partial fulfilment where appropriate, arrange cancellation or refund as required, and record the result. Do not silently replace the black tray with a white one.
Use the stock freshness policy to reduce repeat exceptions, but retain this acceptance check even when feeds update frequently.
6. Connect Dispatch to the Correct Parcel and Items
Collect the carrier, tracking reference, dispatch time and the items in each parcel. Validate a sample tracking link from the customer's perspective before enabling automatic messages.
Distinguish label creation from the later evidence that the parcel entered the delivery network. Decide which event justifies the wording your shop sends.
Avoid a message saying “your entire order has shipped” when only one group has left. Use your installed order and notification tools to represent partial fulfilment accurately, or provide a clear manual update during the pilot.
Test a corrected tracking number. Support needs a way to replace an invalid reference without creating contradictory messages or losing the previous investigation record.
7. Give Exceptions a Daily Review Queue
Review unknown submissions, unaccepted lines and shipments without expected updates at a fixed interval. Add the next action and owner to every exception.
A practical row contains order reference, affected line, customer promise, current supplier evidence, last contact and next review time. “Waiting for supplier” without a follow-up time is not a complete action.
Prioritise by the customer's deadline and financial exposure, not just the oldest ticket. A holiday gift with tomorrow's promised arrival may need attention before an ordinary parcel with a later window.
Use the holiday cutoff guide when seasonal dates apply. Suspend new promises on an affected route while checking existing orders separately.
8. Reconcile Orders, Charges and Refunds
Compare the supplier's invoice or order report with accepted and shipped quantities. Investigate duplicate supplier references, unexpected delivery charges and billed items that were rejected.
Keep customer refunds separate from supplier credits. A refund to the buyer and a credit from the supplier are different transactions and may happen on different dates.
Use the returns workflow to close cases with evidence of both the physical and financial result. Do not close a customer case merely because the supplier promised a future credit.
Retain the reason for each adjustment. A recurring extra-parcel fee may reveal a pricing problem that belongs in the next supplier review.
9. Test the Workflow Before Increasing Volume
Run one normal order, one rejected item, one unknown submission outcome and one split shipment. Include a cancellation before dispatch and a refund case using an appropriate test process.
For each case, ask whether the tracker shows the true state, whether the customer message is accurate and whether the money can be reconciled.
When evaluating automation, reproduce those cases with the actual connector. A demonstration that imports products successfully does not prove that failed order submissions or partial shipments are handled correctly.
Increase volume only when someone can resolve the pilot exceptions without reconstructing the order from several disconnected systems.
10. Common Workflow Problems and Fixes
| Problem | Likely cause | What to check or change |
|---|---|---|
| Duplicate supplier orders | A timeout caused an unverified resubmission | Check the stable reference before retrying |
| Paid orders are never submitted | No owner or scheduled review exists | Reconcile eligible orders against the submission register |
| Wrong variant ships | Mapping uses names or incomplete references | Verify exact variant identifiers and units |
| Customers receive premature dispatch emails | Acceptance was treated as shipment | Separate acknowledgement from parcel handover |
| Supplier invoice exceeds expectations | Partial shipments add charges | Compare charges at parcel and order level |
11. Dropshipping Launch Checklist
- Products and destinations are inside an approved scope.
- References and units have been verified with the supplier.
- Every operational state requires observable evidence.
- Submissions use a stable reference and leave a record.
- Unconfirmed and partially accepted orders enter an exception queue.
- Tracking maps to the correct parcel and order lines.
- Customer refunds and supplier credits can be reconciled separately.
- Failure cases have been tested before increasing volume.
Frequently Asked Questions
Does assigning a supplier in PrestaShop send orders automatically?
Do not assume it does. Establish a manual handoff or verify the behaviour of the connector responsible for order submission, acknowledgement and tracking in your installation.
Can I start dropshipping without an automation module?
Yes, a small pilot can use a controlled manual process if order volume and service promises allow it. Keep a submission register and daily reconciliation so orders are not lost between the shop and supplier.
When should I send an order to the supplier?
Use the payment, risk and order-approval conditions defined for your business. Record that decision explicitly so unpaid, cancelled or held orders are not submitted accidentally.
What should happen after a supplier submission times out?
Treat the outcome as unknown until you check the supplier's records or acknowledgement channel. Reuse the agreed stable reference when retrying, and confirm that the supplier does not create a duplicate.
Can one customer order go to several suppliers?
Yes, if the fulfilment process and customer communication support it. Track each supplier group separately and test the combined shipping charge, arrival promise and partial-refund process.
When is it worth automating the workflow?
Automate when the steps and exception rules are clear enough to test. Choose a connector that demonstrates those cases, rather than choosing solely by the size of the catalogue it can import.