Training Data

From Order Placed to Doorstep: How a Sales Order Moves in VATICO

Đăng vào bởi Gong Elijah

The first time I looked at the CRM and saw an order sitting at RT_SHIP for three days, I did not know what that meant or why it mattered. By the time I understood, the gap it revealed had financial and customer consequences all running in parallel. This post is what I wish someone had walked me through on day one.

A Sales Order is not just a record of a purchase. It is the entry point to a multi-party, time-sensitive operational chain — one where Vatico, a warehousing partner, and multiple logistics courier companies each own distinct pieces of the process, and where the chain breaks silently if any handoff fails. Understanding this chain is foundational to almost everything the data team monitors, builds tickets for, and writes alerts around.

The COD Order Chain: What Actually Happens Between “Order Placed” and “Delivered”

Customer Step 1
Order placed on web

Customer details captured. For COD, no cash collected until delivery.

Vatico (System) Step 2
SO (Sales Order) created in CRM; waybill generated and packing slip sent to warehouse partner simultaneously

If waybill generation fails silently, no pickup is ever booked. If the packing slip is missing, the warehouse partner cannot pack.

Warehouse Partner Step 3
Items picked, packed, and ready for courier pickup

Packing wrong items is the warehouse partner’s responsibility. Vatico’s job is to ensure the warehouse partner received the correct documentation to ship the product.

Logistics Courier Step 4
Driver picks up from warehouse partner; delivers to customer; collects COD payment

Courier no-shows and missed pickups are the courier’s responsibility — but Vatico must still monitor outcomes and follow up. Ignoring it is not an option.

Vatico (System) Step 5
CRM updated; VAT invoice issued same day as delivery

Vietnamese law requires same-day invoicing on delivery. A delayed shipment means a compliance breach. The invoice is issued once and cannot be edited.

Customer Step 6
Parcel received; COD payment collected; order closed

Couriers mark delivery as completed, releasing the money for reconciliation for Vatico. Every day of delay postpones cash reconciliation for Vatico.

Who Is Responsible for What — and Where Vatico’s Boundary Sits

Understanding where Vatico’s responsibility ends and a partner’s begins is essential in order fulfillment — assigning ownership correctly prevents wasted effort and ensures operational bottlenecks are resolved promptly.

Responsibility by Stage
Situation
Who Owns It
Owner
Waybill document is incorrect
Vatico must ensure the waybill is accurate before handing off. If the document is wrong, that is a Vatico error.
Vatico
Packing wrong items
Warehouse partner’s responsibility. Damage and stock issues are handled separately outside pick and pack.
Warehouse Partner
Courier does not show up or cancels pickup
Logistics courier’s responsibility. However, Vatico must monitor the outcome and follow up — Vatico cannot ignore it.
Courier and Vatico
Customer gives wrong address at checkout
Customer responsibility, but cannot be modified once the order enters the system. The system is fully automated post-placement.
Customer
Tax invoice not issued on delivery day
Vatico’s tax compliance obligation. The law is clear — same-day issuance on delivery. Delayed delivery is a compliance risk and a possible fine.
Vatico
Customer communication on delayed delivery
Handled by the customer service bot, which follows the SLA of the delivery partner once informed. Vatico must ensure the bot has the information.
Vatico Customer Service Bot

The cleaner way to remember this: Vatico is responsible for the correctness of the instruction it sends — the shipping documentation, the SO to logistics couriers, the packing slip. What partners do with that instruction is their domain. But if the instruction never arrives, or arrives wrong, or the outcome is not monitored — that is always Vatico’s problem.

The SLAs That Cannot Be Missed

A Service Level Agreement (SLA) is an agreement between a service provider and a customer that defines the specific level of service expected, including performance metrics, responsibilities, and remedies if standards are missed. Several of these are externally enforced and have direct business consequences if breached. As a data team member, these are the thresholds your monitoring and alerting work is ultimately protecting.

SLA Threshold Owner Consequence if Missed
Order to courier handover 3 days from order creation Vatico + Warehouse Partner COD cash flow delayed; customer dissatisfaction spikes
VAT invoice issuance Same day as delivery confirmation Vatico (system) Direct legal exposure to the Tax Authority; cannot retroactively fix once the window passes
COD reconciliation Per finance cycle — couriers remit on a schedule Finance + Data Silent reconciliation failure means cash will not be collected by Vatico
The 3-day handover SLA is not a soft guideline. Orders 7**44 and 7**43 sat at RT_SHIP for 3 days because no alert existed to surface them. By the time they were manually discovered, both the delivery SLA and the VAT invoice window had already been breached. The business impact accumulated entirely before anyone knew the problem existed.

Other Fulfillment Policies Every Intern Should Know

Several Vatico policies define what the system will and will not do once an order is placed. Understanding these upfront saves time — both yours and the customer service team’s.

Orders cannot be modified after placement

Once an order enters the system, Vatico cannot cancel it, change the product or quantity, or edit delivery information. The processing pipeline is fully automated. This is by design to simplify the fulfillment flow. Customers are informed of this before they place the order, but it is important to understand that it is a fundamental constraint when planning to build features for the system.

Refunds are not supported for COD customers who have already paid

If a customer pays on delivery and subsequently wants a refund, the policy does not support this. Returns are governed by a separate process. Knowing this matters for data work because it defines the scope of how you should build any new features in the system

Customer communication follows the Customer Service bot, and serves Customer related needs

Customer-facing communication is handled by the CS bot, which acts when it has information and when the customer asks. As a DA you do not need to consider customer facing communication as it is outside your scope.

References

Gong Elijah