Order – ERP Integration Flow (Process Description)

1. New Order → Order Approved (paid)

When there is a New Order, the Omisell system will verify it and change the status to Order Approved, which means the order has been confirmed for processing — ⚠️ NOT that it has been paid. approve_order only requires the order to HAVE a payment record; it does not require the money to have been collected: a COD order with payment_status = 100 Unpaid can still be approved. Do not raise a "paid" Sales Order off this milestone.

ERP: Generate a Sales Order (SO).

2. Shipment Creation (Delivery Order)

After the order is approved, Omisell will move the order status to Created Shipment.

ERP: Generate a Delivery Order (DO).

3. Cancellation Flow

If the order is cancelled:

Omisell: order status changes to Order Cancelled.

ERP: execute Cancel SO.

4. Shipping & Invoicing

When the order is shipped:

Omisell: status changes to Order Shipped.

ERP: perform Invoice Confirmation and generate an Invoice (IV).

5. Return Flow

If the delivery fails → status changes to Order Returned (Fail Delivery).

If the customer returns the product → status changes to Order Returned (RMA).
In both cases:
ERP: generate a Return Order.

Conclusion:

Implementing all of the above steps helps reduce inventory discrepancies between the ERP and WMS at any given time. However, certain discrepancies may still occur at specific points due to data synchronization issues between the two systems or exceptional cases such as damaged or lost goods.

We provide a Webhook system that allows you to receive order information or status changes in real time. For more details, please refer to Webhook.

ERP Integration Flow

Order – ERP Integration Flow (Process Description)#

1. New Order → Order Approved (paid)#

2. Shipment Creation (Delivery Order)#

3. Cancellation Flow#

4. Shipping & Invoicing#

5. Return Flow#