Direct Fulfillment (DF) vs. FBA for Vendors: When Amazon Lets You Choose
9 January 2026
Cost-to-Serve Analysis: Finding Unprofitable Customers
9 January 2026
OUR GOAL
To provide an A-to-Z e-commerce logistics solution that would complete Amazon fulfillment network in the European Union.
The era of managing logistics via spreadsheets and static carrier contracts is effectively over. For e-commerce businesses scaling beyond a few hundred orders a month, the logistics layer is no longer just a cost center—it is a critical component of the Customer Experience (CX) and a primary driver of operational margins.
Selecting the right Transport Management System (TMS) is arguably one of the most high-stakes decisions a logistics director will make. A robust TMS does not simply print labels; it acts as the central nervous system of your supply chain, orchestrating data flow between your ERP, WMS, carriers, and the end customer.
However, the market is flooded with SaaS solutions promising "seamless integration." To navigate this, you need to look beyond the marketing fluff and interrogate the technical capabilities. Below is a comprehensive checklist of core TMS features required to sustain growth, optimize costs, and maintain delivery performance in a modern e-commerce environment.
1. Advanced carrier connectivity and API agility
The fundamental purpose of a TMS is connectivity. However, "integrates with carriers" is too vague a requirement. You need to assess the depth and quality of these integrations.
Multi-carrier strategy execution
A modern TMS must allow you to switch between carriers instantly without IT intervention. This is crucial for resilience. If your primary carrier suffers a hub outage or a strike, can you reroute traffic to a backup provider with a single click?
- Checklist item: Does the system support pre-built integrations with major global players (DHL, UPS, FedEx) as well as niche, local last-mile couriers relevant to your target markets (e.g., Colissimo in France, InPost in Poland)?
- Checklist item: Are new carrier integrations added via "plug-and-play" modules, or do they require weeks of custom coding?
Real-time API vs. EDI
Legacy systems often rely on EDI (Electronic Data Interchange), which processes data in batches. In the on-demand economy, this is often too slow.
- Checklist item: Prioritize systems that utilize RESTful APIs for real-time rate shopping and label generation. This ensures that the price and delivery promise you see are current, factoring in fuel surcharges or dynamic capacity constraints at that exact moment.
2. Intelligent order routing (The "smart" layer)
This is where a TMS pays for itself. The system should automatically select the best carrier service for every single package based on a complex set of rules defined by your business logic.
Least-Cost Routing (LCR)
The system must automatically compare rates across all integrated carriers for a specific package's dimensions, weight, and destination, selecting the cheapest option that meets the service level agreement (SLA).
- Checklist item: Can the LCR algorithm account for volumetric weight divisors, which vary by carrier?
- Checklist item: Does it factor in hidden surcharges (e.g., residential delivery fees, remote area surcharges) during the comparison?
Service-level rules automation
Cost isn't always the only factor. Speed and reliability matter.
- Checklist item: Can you set rules such as: "If the basket value is over €200, force Express shipping" or "If the destination is Paris intra-muros, offer same-day delivery options"?
- Checklist item: Fail-over logic: If the cheapest carrier is currently experiencing known delays (e.g., flagged via the system), does the TMS automatically default to the next best option to protect the delivery promise?
3. Label generation and documentation compliance
Generating a label sounds simple, but in cross-border e-commerce, it is a minefield of compliance requirements.
High-velocity batch printing
For warehouses processing thousands of orders per hour, latency is the enemy.
- Checklist item: The TMS must support high-volume batch printing with zero lag. It needs to communicate directly with thermal printers (Zebra, Honeywell) without complex driver dialogs slowing down the packing bench.
Cross-border documentation (Paperless trade)
Shipping outside the EU or the US requires commercial invoices and customs declarations (CN22/CN23).
- Checklist item: Does the TMS automatically generate compliant customs documents based on HS codes stored in your product catalog?
- Checklist item: Does it support "Paperless Trade" (ETD), sending customs data digitally to the carrier so packages aren't held up at borders due to missing physical paperwork?
4. End-to-end visibility (Control tower)
Once the package leaves the warehouse, you typically enter the "black hole" of logistics. A competent TMS turns the lights back on.
Normalized tracking events
Every carrier speaks a different language. One might say "Out for Delivery," another " loaded on van," another "last mile scan."
- Checklist item: The TMS must ingest these disparate status updates and normalize them into a single, standardized language (e.g., "In Transit," "Exception," "Delivered"). This allows your support team to view the status of any shipment, regardless of the carrier, on a single dashboard.
Proactive issue detection
Waiting for a customer to complain that their package is lost is a failure of logistics.
- Checklist item: Look for specific alert systems: "Show me all shipments that have been stuck in 'In Transit' status for more than 4 days." This allows proactive intervention (sending a replacement or contacting the carrier) before the customer even notices the delay.
5. Post-purchase experience (Branded tracking)
Marketing does not end at the checkout. The anticipation phase (waiting for the package) has the highest open rates of any email communication.
Branded tracking pages
Sending customers to a generic carrier website (where they might see ads for competitors or confusing logistic jargon) is a missed opportunity.
- Checklist item: Does the TMS provide a white-label tracking page hosted on your domain? This page should display the order status, estimated delivery date (EDD), and—crucially—marketing assets or product recommendations.
Personalized notifications
- Checklist item: The system should trigger SMS or Email updates at key moments: Dispatched, Out for Delivery, and Delivered.
- Checklist item: Exception management: If a delivery attempt fails, the system should automatically email the customer with instructions on how to reschedule or collect from a pickup point, reducing "Where Is My Order" (WISMO) tickets for your customer service team.
6. Reverse logistics management (Returns)
In fashion e-commerce, return rates can hit 30-40%. If your TMS doesn't handle returns efficiently, you are bleeding profit.
Self-service return portals
The manual process of a customer emailing support to ask for a return label is obsolete.
- Checklist item: The TMS should offer a customer-facing portal where users select the items they want to return and the reason why.
Dynamic return routing
Not all returns should go back to the main warehouse.
- Checklist item: Can the system route returns based on condition or location? For example, defective items go to a repair center, while pristine items go to a local store or regional hub for faster restocking.
- Checklist item: QR Code Returns: Does the system support "printer-less" returns, where the customer shows a QR code at a drop-off point (PUDO) instead of printing a label at home?
7. Logistics business intelligence (Analytics)
You cannot improve what you cannot measure. A TMS sits on a goldmine of data regarding carrier performance and shipping costs.
Carrier performance scorecards
- Checklist item: You need objective data to negotiate contracts. The TMS should visualize: What is the actual on-time delivery percentage for Carrier X versus Carrier Y? What is their loss/damage ratio?
Cost-to-serve analysis
- Checklist item: The system should provide granular visibility into shipping spend. Can you see the average shipping cost per country, per SKU, or per volumetric weight bucket? This data is essential for finance teams to audit carrier invoices against quoted rates to find discrepancies.
8. Integration ecosystem (ERP & WMS)
A TMS operating in a silo is useless. It must shake hands with your existing tech stack.
Bi-directional data flow
It’s not enough to pull order data from the ERP. The TMS must push tracking numbers, shipping costs, and status updates back to the ERP/WMS.
- Checklist item: Verify the "write-back" capabilities. When a label is generated, does the WMS immediately know that the order is "Shipped" so inventory is decremented and the order is closed?
Scalability and cloud architecture
- Checklist item: Is the solution cloud-native (SaaS)? During peak seasons (Black Friday, Cyber Monday), order volumes can spike 10x. Your TMS infrastructure must auto-scale to handle this load without crashing or slowing down label generation.
Turning logistics into a competitive advantage
When evaluating these features, it is vital to adopt a mindset of future scalability. A feature that seems "nice to have" today—such as carbon footprint calculation or AI-driven delivery prediction—may become an industry standard within 18 months.
The goal of implementing a TMS with this specific feature set is to move logistics from a reactive state to a proactive strategic asset. By automating the complex decision-making processes regarding carrier selection and documentation, you free up human capital to focus on the anomaly management and strategic improvements that drive long-term growth.
Ultimately, the right TMS works invisibly. Your warehouse team packs faster, your finance team audits faster, and your customer gets their package on time, every time. That is the definition of logistical excellence.
