You can integrate your marketplace seller account with your DealPOS system by using omni.dealpos.app. One of the marketplaces that can be integrated with DealPOS is the Tokopedia channel. In the marketplace integration, Tokopedia certainly has a different order flow from other channels that already support marketplace integration such as Shopee, Lazada, and WooCommerce.
To see how the transactions flow from Tokopedia recorded to the DealPOS, you can see the table and the steps below
I. Status Order Flow
Tokopedia | DealPOS | Description |
The customer has paid for the order. | Sales order created
| This incoming order requires prior confirmation by the seller and this unconfirmed order has not yet become an Invoice |
The seller confirmed the order. | Invoice Created the status of unpaid payment and unsent delivery | Unpaid and unsent status because the order has not been sent and the customer has not received the order, and stock will still be reduced (allocated) even though the seller has not received the order |
An order has been sent (has been picked up by the courier) | Invoices whose delivery status is unsent will be sent | The delivery status will immediately be sent when the item is already on the expedition or taken by the courier |
Customers already confirm that the order is already complete invoices | Invoices that were previously unpaid payment status will become paid | When the customer has pressed accept the order then at DealPOS the payment status will be paid |
If there is a new order by the customer and waiting for the seller's confirmation, the order will be entered into the New Order tab :
If the order has been confirmed by the seller, the transaction will be recorded in the Ready to Ship tab:
Notes:
The invoice was created as the payment status will be set to Unpaid and the Fulfillment status will be Unsent.
If the order has been sent by logistics, the transaction will be recorded in the In Delivery tab:
Notes:
Payment status will be Unpaid and Delivery status will be Sent.
If the order has been received by the customer and the transaction has been completed by the customer, the transaction will be recorded in the Order Completed tab :
Notes:
Payment status will be Paid and Delivery status will be Sent.
II. Cancel Order Flow
Tokopedia | DealPOS | Description |
Customer cancels order | The invoice that has been made will go to the recycle bin | For invoices that have been created and then canceled, they will be automatically deleted and go to the recycle bin |
Seller cancel order | The invoice that has been made will go to the recycle bin | For invoices that have been created and then canceled, they will be automatically deleted and go to the recycle bin |
If an order is canceled by the buyer or seller, the order will be recorded in the Canceled tab:
Notes:
If the customer cancels the order when the goods have not been shipped, the invoice will be automatically voided.
III. Return Order Flow
Tokopedia | DealPOS | Description |
Customer submits returns | In DealPOS, the transaction will be considered complete with the status of delivery sent and payment paid | If there is a return, a manual edit is needed on the invoice in DealPOS |
If there is an order that is complained about to be returned, it will be recorded in the Complained tab :
IV. Status Code Detail
Status Code | Description | DealPOS | Realtime | Download |
0 | Seller cancel order. | Delete/Void Invoice | Yes | Yes |
3 | Order Reject Due Empty Stock. | Delete/Void Invoice | Yes | Yes |
5 | Order Canceled by Fraud | Delete/Void Invoice | Yes | Yes |
6 | Order Rejected (Auto Cancel Out of Stock) | Delete/Void Invoice | Yes | Yes |
10 | Order rejected by seller. | Delete/Void Invoice | Yes | Yes |
15 | Instant Cancel by Buyer. | Delete/Void Invoice | Yes | Yes |
100 | Order Created. |
| No | No |
103 | Wait for payment confirmation from third party. |
| No | No |
220 | Payment verified, order ready to process. | Create Sales Order | Yes | Yes |
221 | Waiting for partner approval. |
| No | No |
400 | Seller accept order. | convert sales order to invoice | Yes | Yes |
450 | Waiting for pickup. |
| No | No |
500 | Order shipment. | Create outbound logistics | Yes | Yes |
501 | Status changed to waiting resi have no input. |
| No | No |
520 | Invalid shipment reference number (AWB). |
| No | No |
530 | Requested by user to correct invalid entry of shipment reference number. |
| No | No |
540 | Delivered to Pickup Point. |
| No | No |
550 | Return to Seller. |
| No | No |
600 | Order delivered. |
| No | No |
601 | Buyer open a case to finish an order. |
| No | No |
690 | Fraud Review |
| No | No |
700 | Order finished. | Payment invoice | Yes | Yes |
Notes:
This status code detail table will show you the detailed status of the omnichannel integration. It can be used whenever we get an error through the integration and it also helps the developer team troubleshoot the issues
[Tutorial Video] Marketplace Order Flow
Related Articles
If you are looking for another marketplace Order Flow you can see Order Flow channels Shopee, WooCommerce, and Lazada
If you have products on Marketplace and want to download them into POS, you can try to read the Not in POS (Download Product From Marketplace) article.
or You can see other full articles related to the Marketplace
