One Order, Multiple Deliveries: How PrestaShop Plans to Simplify Complex Order Management

Why Does Order Splitting Cause Complications?

Imagine an online store that sells products from different categories – for instance, large household appliances alongside small accessories. A customer adds a refrigerator (which requires special delivery) and a set of tableware (that can be sent by regular mail) to their cart. In the current version of PrestaShop, such items are automatically split into two separate orders, each assigned to different shipping methods.

For the customer this means:

• Confusion: “Why did I receive two order numbers? How do I track my shipments?”
• Dissatisfaction: “I paid for everything together, so why is the total split into parts?”

For the seller this results in:

• Data synchronization challenges in the ERP system (Enterprise Resource Planning, which integrates finances, logistics, warehousing, and other processes).
• Additional workload: Two orders mean checking statuses twice, communicating with the customer separately, and reconciling reports.

The main problem with the current PrestaShop system isn’t the delivery itself—it’s that the platform “breaks” the order into pieces to meet different shipping conditions. This outdated approach no longer meets market demands. However, the PrestaShop team is already working on improvements.

The Current System: Why One Order ≠ One Delivery

Today, PrestaShop automatically splits the cart when items require different shipping services. For example:

• Product A (large-sized) → Delivered by freight.
• Product B (small-sized) → Delivered by courier.

Behind the scenes:

1. The system creates two independent orders.
2. Each order receives its own ID, tracking number, and payment status.
3. To the customer, these appear as two separate purchases.

Why is this inconvenient?

• For the customer: It’s impossible to track the entire order in one place. Returning part of an order becomes a puzzle.
• For the seller: Data is fragmented in the ERP system. Orders must be manually linked, leading to potential errors.
• For marketing: Discounts apply separately to each “mini-order” rather than the total purchase, possibly causing the customer to miss out on savings.

The Future of PrestaShop: One Order – Multiple Deliveries

The PrestaShop team is considering a new concept: a unified order with flexible “Fulfillment Units.”

How It Could Work:

1. The customer sees one order.

   • In the cart: A refrigerator (handled by freight) + a set of tableware (sent by mail).
   • During checkout, the system presents two delivery options without splitting the order.
   • After payment, the customer receives a single order number with two tracking numbers in their account.

2. A new logic: From orders to “logistic groups.”

   • Fulfillment Unit – a group of items with the same shipping conditions.
     Example:
     • Group 1: Large appliances → Delivered by truck (e.g., via DPD).
     • Group 2: Small items → Delivered by courier (e.g., via UPS).
   • Carrier Rules – rules that automatically allocate items into groups based on weight, dimensions, and shipping zone.

3. Technical Changes:

   • A new entity in the database – Fulfillment – is linked to the order but independent from it.
   • A unified financial model: discounts, taxes, and payments are calculated for the entire order rather than separate parts.
   • An API for integration with ERP/WMS (Warehouse Management System) so that data for different deliveries is transmitted within a single order object.

Example: The “HomeComfort” Store and Its Battle Against Chaos

Situation Before the Changes:

• A customer orders a refrigerator (150 kg) and a set of tableware.
• PrestaShop creates two orders:
  • Order #45: Refrigerator → Freight delivery (tracker 1XQ).
  • Order #46: Tableware → Postal service (tracker Z9R).
• The customer panics: “I paid for everything together! Where did my money go?”
• The “HomeComfort” manager spends an hour explaining and manually merging the orders in the ERP system.

Situation After the New System is Implemented:

• Order #45 contains two “Fulfillment Units:”
  • Fulfillment Unit 1: Refrigerator → Truck delivery (DPD). Status: In transit.
  • Fulfillment Unit 2: Tableware → Postal service (UPS). Status: Delivered.
• In the ERP system, the order is displayed as a single entity with subdivisions.
• The customer is satisfied: all information is in one place, and there is no confusion regarding payment.

Why Is This Important?

1. For Customers:

   • Transparency: One order number with multiple trackers – everything is available in the personal account.
   • Simplified Returns: Customers can return part of an order without canceling the entire payment.

2. For Business:

   • Reduced Support Load: Fewer calls to explain why an order “split up.”
   • ERP Compatibility: Data for different deliveries is tied to one ID, making integration more predictable.
   • Marketing Opportunities: Discounts based on the total order value (e.g., “20% off on purchases over €500”) work correctly.

3. For Developers:

   • Simplified Payment Modules: One transaction instead of multiple ones.
   • Flexible API: External systems (such as TMS – Transport Management System) receive detailed data without having to parse multiple orders.

Challenges and Prospects

While the idea is logical, its implementation will require:

• Careful architectural planning: To ensure the new logic does not negatively impact existing modules and integrations.
• Thorough testing: To verify that changes do not disrupt operations, especially for large stores.
• Community training: Merchants and developers accustomed to the old system will need clear guides and documentation.

An alternative might have been to improve the current system by “patching” its shortcomings. However, that would be like endlessly repairing an old house. The new approach offers a more robust solution for the future.

Why Does the Market Need This?

According to Salesforce, 80% of buyers believe that the delivery experience is as important as the product quality. The new PrestaShop concept is a step toward a customer-centric commerce model, where complex logistical scenarios no longer become a headache for everyone involved.

“PrestaShop, as an open-source platform, has always balanced flexibility with simplicity. The new approach isn’t a revolution but an evolution that meets modern market demands. Yes, the changes will take time and effort, but they will help the platform remain competitive in a world where customers value convenience and transparency.”

Which approach seems more viable to you: transitioning to a ‘unified order’ model or gradually improving the existing system? Share your thoughts in the comments.