Samsung México — Logistics & Fulfillment Integration
A logistics backend for Samsung México's e-commerce that grew from a Zebra printer integration into multi-carrier orchestration, shipment status synchronization and inventory checks.
At a glance
- 01Problem
- Samsung México's e-commerce orders had to reach the physical warehouse operation, five delivery providers and the enterprise systems, with shipment status flowing back to the storefront.
- 02My responsibility
- I led the implementation and evolution of the logistics integration backend, developed the original Zebra printer integration from scratch, and led one developer on this workstream while staying hands-on.
- 03Architectural challenge
- The backend sits between e-commerce, warehouse inventory, carriers and enterprise systems. Each order needs stock confirmed, a carrier chosen and a label printed, and every carrier event has to reach the ERP and VTEX.
- 04Outcome
- A logistics backend that evolved from a printer integration into rule-based carrier selection, shipment status synchronization and inventory-aware fulfillment.
Architecture
One backend between e-commerce, inventory, carriers and the warehouse
E-commerce
- VTEXOrders in; shipment status back
Logistics backend
- Logistics backend · Java / Spring Boot
- Receives and processes orders
- Checks inventory availability
- Rule-based carrier selection
- Generates shipping guides and labels
- Propagates shipment status
- Logistics backend · Java / Spring Boot
Enterprise, carriers and fulfillment
- Microsoft Dynamics 365 Business CentralRack inventory availability
- Enterprise ERPExisting ERP kept in step with shipment status
- CarriersFedEx, DHL, Estafeta, 99 Minutos, Samsung Delivery
- Zebra printersShipping labels and operational printouts
Physical fulfillment
Core mechanism
Rule-based carrier selection
For each order, the backend chooses between FedEx, DHL, Estafeta, 99 Minutos and Samsung Delivery using rules based on distance, product and operational criteria. In its later form it first confirms in Business Central that stock is available. Selection stays in the backend: Business Central answers whether there is inventory, and does not choose carriers or run the logistics logic.
Evolution of the solution
From a printer integration to a logistics backend
Order to shipping label
- 01VTEX orderA new order arrives
- 02Logistics backendReceives and processes it
- 03Business CentralIs inventory available?
- 04Carrier selectionRules: distance, product, operational criteria
- 05Guide and labelGenerated for the selected carrier
- 06FulfillmentThe package is prepared and shipped
Shipment status synchronization
- 01CarrierShipment status update
- 02Logistics backendReceives and processes the change
- 03Enterprise ERPStatus propagated
- 04VTEXOrder shows the current state
Zebra fulfillment integration
When I joined, I developed the first integration with Zebra printers from scratch using the Zebra SDK. The printers produce shipping labels and guides, plus operational tickets and labels. It was the first automation connecting the e-commerce software with the physical fulfillment operation.
Multi-carrier orchestration
The project grew into a backend that integrates FedEx, DHL, Estafeta, 99 Minutos and Samsung Delivery, and selects the carrier for each order automatically with rules based on distance, product and operational criteria.
Order and shipment status synchronization
The backend receives shipment status updates from the carriers and propagates the corresponding status through the enterprise ERP to VTEX, keeping the e-commerce and enterprise systems aligned with carrier events.
Business Central inventory integration
Later, Samsung adopted a basic Microsoft Dynamics 365 Business Central setup to manage physical rack inventory. The backend integrated with it rather than being replaced: when an order arrives, it checks availability in Business Central, and only if stock is available does it select the carrier and generate the shipping guide and label.
For technical readers
Technical detail
Context
Samsung México's e-commerce operation on VTEX, during my role at Cheil México. The work started as an integration between the e-commerce software and the Zebra printers of the physical fulfillment operation, and evolved into a logistics backend between VTEX, the enterprise systems, five delivery providers and, later, Business Central inventory.
Responsibility
- Led the implementation and evolution of the logistics integration backend.
- Developed the original Zebra integration from scratch with the Zebra SDK.
- Implemented the carrier and enterprise-system integrations, and the automatic carrier-selection logic.
- Integrated order and shipment status flows across carriers, the enterprise ERP and VTEX.
- Led one developer on this workstream while remaining hands-on in development and production support.
Complexity
- Software with a physical effect: labels and operational printouts in a real warehouse.
- Five delivery providers behind one selection step.
- Shipment state that has to stay consistent across carriers, the enterprise ERP and VTEX.
- A new inventory system, Business Central, introduced into an existing logistics flow.
Architecture
- A Java and Spring Boot backend between VTEX, the enterprise systems, the carriers and the Zebra printers.
- Business Central is consulted for rack inventory availability; it is not the source of the logistics logic.
- The existing enterprise ERP receives the shipment status propagated from carrier events.
Result
- Automated fulfillment steps that were previously manual, starting with label printing.
- Connected e-commerce, inventory and carrier operations in one backend.
- Enabled rule-based carrier selection across five delivery providers.
- Synchronized shipment status across carriers, the enterprise ERP and VTEX.
- Integrated rack inventory availability into the shipping flow.