--- title: "TMS Platforms That Integrate With Shopify, Amazon and E-Commerce Marketplaces: What Integration Requires in 2026" id: "27769" type: "post" slug: "tms-integration-shopify-amazon-ecommerce-marketplaces-2026" published_at: "2026-10-28T13:30:00+00:00" modified_at: "2026-10-28T17:17:35+00:00" url: "https://locus.sh/blogs/tms-integration-shopify-amazon-ecommerce-marketplaces-2026/" markdown_url: "https://locus.sh/blogs/tms-integration-shopify-amazon-ecommerce-marketplaces-2026.md" excerpt: "How a TMS integrates with Shopify, Amazon and Walmart Marketplace: three integration patterns, what each platform requires back and what to ask a vendor." taxonomy_category: - "General" --- [General](https://locus.sh/blogs/category/general/) # TMS Platforms That Integrate With Shopify, Amazon and E-Commerce Marketplaces: What Integration Requires in 2026 [Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/) Last updated: Oct 28, 2026 15 mins read A TMS integrates with Shopify, Amazon and other e-commerce platforms in one of three ways: a native connector maintained by the TMS vendor, an API integration built on the platform’s order and fulfillment APIs, or a middle layer such as an order management system or integration platform that sits between the storefront and the TMS. Whichever pattern is used, something must read the order and write back the ship confirmation, the carrier’s identity and a tracking number the platform can validate, and each platform measures sellers on those messages, so a late or malformed write-back can cost a seller listings even when the parcel arrives on time. This guide is a vendor-neutral reference for integration and IT leads at enterprise e-commerce shippers, and it states plainly that Locus, the world’s first Decision-Intelligent, Agentic TMS, documents no native Shopify, Amazon or Walmart connector. ## Key Takeaways - A TMS connects to a storefront through a native connector, a direct API integration or a middle layer, and each has a different owner for the maintenance. - Amazon’s seller-fulfilled targets are a late shipment rate below 4%, valid tracking above 95% and cancellations below 2.5%, and Walmart requires valid tracking of 99% or above. - Shopify’s fulfillment write-back defaults to not notifying the customer, and its webhooks arrive more than once and unordered. - Each platform needs a carrier code and tracking number it can verify, and Amazon’s “Other” fallback stops tracking updates. - Write-back is a queueing problem: at Amazon’s documented 2 requests per second, confirming 5,000 shipments takes about 42 minutes. - Locus publishes a slots and promise API and ShipFlex, but no native Shopify, Amazon or Walmart connector. ## How Was This Guide Written? This guide compares integration patterns and platform requirements, not vendors, and it names no competitors. It draws on Amazon’s, Shopify’s and Walmart’s published seller and developer documentation. Amazon’s help pages could not be read directly, so the Amazon thresholds come from Amazon’s seller blog and staff posts in Seller Central forums and should be confirmed in Seller Central before you build to them. Claims about Locus were checked against locus.sh pages on October 28, 2026. We review the guide every 30 to 60 days. ## How Do TMS Platforms Integrate With Shopify, Amazon and Other E-Commerce Platforms? A TMS integrates through a native connector, a direct API integration or a middle layer, and the choice decides who builds, who maintains and who is accountable when a platform changes its rules. | | Native connector | Direct API integration | Middle layer | | --- | --- | --- | --- | | What it is | A prebuilt integration maintained by the TMS vendor | An integration built by the shipper, the vendor or a partner on the platform’s order and fulfillment APIs | An OMS, integration platform or multichannel shipping tool between storefront and TMS | | Who maintains it | The TMS vendor | Whoever built it, usually the shipper’s IT team | The middle-layer vendor | | Strength | Fastest start for the platforms it covers | Full control over fields, timing and retries | One integration can serve several storefronts | | Risk | Covers only the platforms the vendor chose; limited control of timing | Build and upkeep cost; you own queueing, idempotency and monitoring | Another system and vendor in the path; added latency | | What to ask | Which platforms, which operations and which carrier codes are covered, and how fast a platform change is handled | Which APIs are documented, what rate limits apply and who owns reconciliation | Which write-back operations it supports and who is accountable for late confirmations | For most enterprise shippers the real answer is a mix. A native connector handles the common path, direct API work covers the exceptions, and a middle layer appears where several storefronts and marketplaces feed one carrier network. The rest of this guide covers what any of the three must do. | Also Read: 5 Critical Shipping API Integration Categories for Enterprise Logistics in 2026 | | --- | ## Why Does Marketplace Write-Back Matter? The Business Case Marketplaces turn shipping events into account health, and the thresholds are published. - Amazon’s seller guidance says seller-fulfilled sellers should keep the [late shipment rate below 4%](https://sell.amazon.com/blog/selling-policies) , the pre-fulfillment cancel rate below 2.5% and the order defect rate below 1%, and Amazon staff state that the metric counts ship confirmations completed after the expected ship date. - Amazon staff say the valid tracking target is [over 95%](https://sellercentral.amazon.com/seller-forums/discussions/t/f77d562d-ffae-41c5-80de-ca694cc22414) , that a tracking ID is valid if Amazon records at least one carrier scan, and that the rate covers packages shipped and confirmed over 30 days. - Amazon’s on-time delivery rule requires [a minimum of 90%](https://sellercentral.amazon.com/seller-forums/discussions/t/bb76566a-c8a4-468d-bb94-d49402c83023) for seller-fulfilled products, with an update effective 28 February 2026 saying only the listings most affected by a drop are deactivated. - Walmart’s seller standards, last updated 28 July 2026, require [valid tracking of 99% or above](https://marketplacelearn.walmart.com/guides/Policies%20&%20standards/Performance/Seller-performance-standards) , on-time delivery of 90% or above, cancellations of 2% or below and late shipment of 5% or below. - The FTC’s order merchandise rule requires a seller to have a reasonable basis to ship within the stated time or [30 days after the order](https://www.ecfr.gov/current/title-16/chapter-I/subchapter-D/part-435) , to offer the buyer a choice to consent to a delay or cancel, and to refund promptly, defined as within 7 working days. | Also Read: Delivery Slot Promising at Shopify Checkout: How Rate Tools Like ShipperHQ and nShift Integrate, and Where Live Capacity Fits in 2026 | | --- | ## What Do Amazon, Shopify and Walmart Marketplace Require Back From a TMS? The three platforms need the same core facts, a carrier, a tracking number and a ship time, but they differ in the call, the scoring and the limits. | Aspect | Amazon (seller-fulfilled) | Shopify | Walmart Marketplace | | --- | --- | --- | --- | | Write-back call | Orders API confirmShipment, one call per package | fulfillmentCreate mutation with trackingInfo | Ship Order Lines API, per order line | | Required fields | Carrier code, tracking number, ship date, package reference ID, order items; carrier name if code is Other | Line items by fulfillment order; tracking company, number and URL are optional inputs | Ship date and time, carrier, method code, tracking number; tracking URL if carrier is other | | What the platform scores | Late shipment under 4%, valid tracking over 95%, cancellations under 2.5%, on-time delivery 90% | No seller scorecard; merchant brand experience | Valid tracking 99%, on-time delivery 90%, late shipment 5%, cancellations 2% | | Timing anchor | Ship confirmation against the order’s latest ship date | Merchant-defined | Marked shipped against the expected ship date; carrier first scan also used | | Tracking validation | At least one carrier scan; carrier must match | Shopify builds links for known carriers and does not update shipment status itself | At least one valid carrier scan; approved or integrated carriers | | Carrier list | 594 carrier codes, with “Other” and no tracking updates | 115 tracking company names, unknown names accepted | About 60 approved parcel carriers plus an enumeration in the API | | Rate limit on write-back | 2 requests per second, burst 10 | GraphQL points: a mutation costs 10, Standard plan 100 points per second | 429 on exceeding limit | | Inbound events | Notifications API, with a recommendation to be able to retrieve data after an outage | Webhooks: 5-second timeout, 8 retries over 4 hours, no ordering guarantee | Order management API statuses | ## How Does Marketplace Write-Back Work, and Where Does It Break, in Seven Steps? The seven steps follow an order from platform to carrier and back, and each has a failure mode. ### 1. Ingest the order and acknowledge it Amazon’s Notifications API lets a seller receive events such as ORDER_CHANGE instead of polling, and it recommends keeping a way to retrieve data after an outage. Shopify’s webhooks must be answered within five seconds, so queue the payload and process it asynchronously, and Walmart orders move through Created, Acknowledged and Shipped. ### 2. Allocate to a carrier and create the label The decision about which carrier carries the order sets everything that follows, because each platform validates the carrier. Walmart says shipping with a non-approved carrier can lead to suppression because tracking cannot be validated. ### 3. Map your carrier to each platform’s carrier code Keep a mapping table per platform. Amazon’s carrier enumeration holds 594 values, and using Other with a carrier name means Amazon cannot track the package. Shopify accepts unknown company names but advises sending company and URL together, and Walmart requires a valid tracking URL when the carrier is other. ### 4. Send the ship confirmation Amazon confirmShipment needs the carrier code, tracking number, ship date, a package reference ID and order items per package, and resubmitting with the same package reference ID edits the shipment. Shopify’s fulfillmentCreate defaults notifyCustomer to false, so decide who sends the shipping email. Walmart’s Ship Order Lines API requires ship date and time, carrier, method code and tracking number. ### 5. Choose the moment of confirmation Timing rules differ. Walmart says to send tracking only once a package has been tendered to the carrier, and an order marked shipped after the expected ship date is late even if the carrier scan is quick. Amazon counts a ship confirmation after the expected ship date as late, and counts tracking as valid only after a carrier scan. Confirm before the cut-off, but only for parcels that are actually in the carrier’s hands. ### 6. Queue, throttle and make writes idempotent Treat write-back as a queue with retries. Amazon allows 2 requests per second with a burst of 10, Shopify’s webhooks arrive more than once and unordered, and Shopify advises deduplicating on the webhook ID and running reconciliation jobs. Use an idempotency key per package so a retry never creates a second shipment. ### 7. Monitor the metrics and reconcile daily Build a daily report of orders shipped but not confirmed, confirmed with no carrier scan, invalid tracking and confirmations after the expected ship date. These are the inputs to each platform’s score, so catch them before the platform does. | Also Read: How to Evaluate Carrier API Quality: A Technical Guide for Logistics Teams in 2026 | | --- | ## What Should You Ask a TMS Vendor About E-Commerce Platform Integration? Five questions separate a TMS that can keep marketplace metrics healthy from one that only plans freight, and each can be asked in a demo. ### Which integration pattern covers each of your storefronts? Ask for a list by platform: native connector, API integration or middle layer. A vendor that cannot say which pattern applies to Shopify, Amazon and Walmart has not scoped the work. ### Is there a carrier-code mapping per platform? The system should hold a maintained mapping from your carriers to each marketplace’s codes and flag any carrier that falls back to Other or is not on an approved list. ### Does it confirm per package with idempotency? Multi-package orders need one confirmation per package with stable reference IDs, so retries edit and do not duplicate. ### Does the queue respect rate limits and ship-by times? Look for a queue that respects each platform’s limits, prioritizes orders near their ship-by time and reports backlog. ### Can it monitor platform metrics and match promise dates? The system should compute proxies for valid tracking, late shipment and on-time delivery from your own events and alert before a threshold is crossed. The expected ship and delivery dates you promise should also match the dates the platform uses, since a mismatch creates late shipments that are no one’s fault. | Also Read: EDI to API: Mapping the Core Freight Messages (204, 990, 214, 210, 856) to Their API and Webhook Equivalents in 2026 | | --- | ## What Do the Numbers Imply for Write-Back in Practice? **A queueing example on documented limits.** The figures are arithmetic from the platforms’ published rates, and your account limits may differ. Suppose 5,000 shipments are tendered to carriers at 13:30 and the platform’s ship-by cut-off is 14:00. | Platform | Documented limit | Time to write back 5,000 confirmations | | --- | --- | --- | | Amazon confirmShipment | 2 requests per second, burst of 10 | About 42 minutes, so the last confirmation lands around 14:12 | | Shopify fulfillmentCreate, Standard plan | 100 points per second, 10 points per mutation | About 8 minutes at roughly 10 mutations per second | | Shopify fulfillmentCreate, Plus plan | 1,000 points per second | About 50 seconds at roughly 100 mutations per second | On Amazon the queue alone pushes the tail of the wave past the cut-off, which would count as late even though every parcel left on time. The fixes are earlier confirmation as each parcel is scanned, ordering the queue by ship-by time and sending as handoff happens rather than in a batch. **An ASEAN apparel retailer.** The retailer’s last mile ran almost entirely through carriers, each reporting its own status codes, and every new carrier had been a full engineering project. Locus harmonized carrier statuses into one standard set, synced to the OMS and WMS, and the retailer reported more than 40% fewer WISMO and returns queries and carrier onboarding down from three months to three days. The case is not a marketplace integration, but it shows why one standard status model makes write-back simpler. [Read the apparel case study](https://locus.sh/case-studies/apparel-multi-carrier-parcel-management/) . **A Canadian grocery brand.** The brand’s Locus agents create the order and label through APIs integrated with every contracted 3PL the moment a shipment is ready, and track each shipment to proof of delivery. It reported 25% less time on manual shipping tasks and 15% lower fulfillment costs. The case is not a marketplace either, but automatic labels and tracking are the inputs a write-back needs. [Read the Canadian grocery case study](https://locus.sh/case-studies/grocery-carrier-orchestration/) . ## What Mistakes Do Teams Make When Integrating a TMS With Marketplaces? Four mistakes recur. **Confirming at label creation, not at handoff.** Walmart wants tracking only once the carrier has the parcel, and Amazon counts tracking as valid after a carrier scan. **Letting carriers fall back to Other.** On Amazon, Other means no tracking updates, and on Walmart a non-integrated carrier can miss the 99% target. **Assuming Shopify updates delivery status.** Shopify builds tracking links for known carriers but does not automatically update the shipment status, so your system must send events. **Ignoring the consumer-protection clock.** The FTC rule requires a revised date or a chance to cancel when you cannot ship on time, so delayed orders need a notification path. | Also Read: API Integrations for Logistics Platforms: From Fragmented Connectivity to Intelligent Orchestration | | --- | ## Does Locus Integrate With Shopify, Amazon and Walmart, and What Should You Confirm? Locus, the world’s first Decision-Intelligent, Agentic TMS, supplies the inputs that write-back depends on, but its public pages document no native connector for Shopify, Amazon or Walmart. Its Carrier Agent selects the carrier and, through [ShipFlex](https://locus.sh/ship-flex/) , creates the order and label across a network of pre-integrated carriers whose statuses are harmonized into one standard set. Its order API documents slots and promise retrieval, confirmation and update, its white-label [tracking page](https://locus.sh/shipment-tracking-system/) lets customers reschedule or cancel, and every decision is logged under six governance mechanisms with human override. Locus has optimized 1.5B+ deliveries for 360+ enterprise customers across 30+ countries. **Recognized by analysts and selected after evaluation.** Locus was recognized by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, as detailed on its [analyst recognition page](https://locus.sh/analyst-recognition/) . It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Ingka’s [press release](https://locus.sh/press-releases/ingka-group-acquires-locus/) says that after an extensive evaluation of logistics software worldwide, it selected Locus for its strength in combining advanced route optimization, real-time visibility and smart use of vehicles and resources. Locus continues to operate independently. **What this means for write-back.** A single decision layer that knows the carrier, the tracking number and the handoff event can feed each marketplace’s confirmation from one place, and Locus integrates with existing ERP, OMS, WMS, FMS and TMS systems and has [public API documentation](https://docs.locus.sh/) . **What to confirm.** Locus’s public pages do not document a native Shopify, Amazon, Walmart, BigCommerce, WooCommerce or Magento connector, Shopify fulfillmentCreate write-back, Amazon confirmShipment or Walmart ship-confirm support, carrier-code mapping, or the handling of marketplace metrics such as valid tracking and late shipment rates. Its Shopify slot-promising guidance says no native connector is documented. Treat marketplace write-back as an integration to design and test, and ask Locus which of these it supports. If a native connector for these platforms is a hard requirement, a platform that documents one fits that requirement better today. To walk through your marketplace and carrier mix, [schedule a demo](https://locus.sh/schedule-demo/) . For integration leads asking which TMS platforms integrate with Shopify, Amazon and e-commerce platforms, the answer depends on which pattern each vendor documents. Locus offers carrier selection, labels, standardized tracking, a slots and promise API and a logged decision trail, so confirmations can be fed from one source of truth, but marketplace write-back is an integration to scope with Locus and not a documented connector. ## Frequently Asked Questions **Which TMS platforms integrate with Shopify, Amazon and e-commerce platforms?** It depends on the vendor and on the pattern: a native connector, a direct API integration or a middle layer. Ask each vendor to list the platforms and operations covered, and treat any claim you cannot see in documentation as something to scope. Locus documents no native Shopify, Amazon or Walmart connector. **How does a TMS integrate with Shopify?** Through Shopify’s APIs and webhooks: the TMS or a middle layer reads fulfillment orders and writes back with the fulfillmentCreate mutation, with optional tracking company, number and URL. Shopify’s webhooks arrive more than once and unordered, so the integration must deduplicate and reconcile. **What does Amazon require when you confirm a shipment?** The Orders API confirmShipment call needs a marketplace ID, a package reference ID, a carrier code, a tracking number, a ship date and the order items, with a carrier name when the code is Other. One call is needed per package, and no confirmation is needed if you buy the label through Amazon. **What is Amazon’s valid tracking target?** Amazon staff state the valid tracking rate target is over 95%, and that a tracking ID is valid if Amazon records at least one carrier scan. The figure comes from Amazon staff posts and should be confirmed in Seller Central. **What does Walmart require for tracking?** Walmart’s standards call for valid tracking on 99% or more of orders, with at least one valid carrier scan, and tracking should be sent only after the package is tendered to the carrier. Using a non-approved carrier can lead to suppression because Walmart cannot validate the tracking. **Do marketplaces check how fast you confirm shipments?** Yes. Amazon counts a ship confirmation completed after the expected ship date as late, and Walmart counts an order marked shipped after the expected ship date as late even if the carrier scan is quick. Queue and rate limits can therefore create late shipments. **Does Locus have native Shopify, Amazon or Walmart connectors?** Locus’s public pages do not document native connectors for these platforms. They document an order API with slots and promise operations and carrier orchestration through ShipFlex, so marketplace write-back should be scoped and confirmed with Locus. MEET THE AUTHOR Ishan Bhattacharya Lead - Content Ishan, a knowledge navigator at heart, has more than a decade crafting content strategies for B2B tech, with a strong focus on logistics SaaS. He blends AI with human creativity to turn complex ideas into compelling narratives. [https://locus.sh/blogs/fareye-alternatives/](https://locus.sh/blogs/fareye-alternatives/) [General](https://locus.sh/blogs/category/general/) ## [Top 10 FarEye Competitors to Consider in 2026 for Better Delivery Performance](https://locus.sh/blogs/fareye-alternatives/) Compare the top 10 FarEye alternatives for 2026. Review routing, visibility, delivery orchestration, pricing, and use cases to find the best fit for your team. [Anas T](https://locus.sh/blogs/author/anas_locus/) Last updated: Oct 28, 2026 [Read more](https://locus.sh/blogs/fareye-alternatives/) [https://locus.sh/blogs/ai-for-last-mile-delivery-costs/](https://locus.sh/blogs/ai-for-last-mile-delivery-costs/) [AI in Action at Locus](https://locus.sh/blogs/category/ai-in-action-at-locus/) ## [AI in Last-Mile Delivery: 7 Cost-Cutting Strategies for 2026](https://locus.sh/blogs/ai-for-last-mile-delivery-costs/) Uncover 7 ways AI is minimizing last-mile delivery costs in 2025. Improve logistics performance with advanced automation and predictive analytics effortlessly. [Mrinalini Khattar](https://locus.sh/blogs/author/mrinalini/) Last updated: Oct 28, 2026 [Read more](https://locus.sh/blogs/ai-for-last-mile-delivery-costs/) TMS Platforms That Integrate With Shopify, Amazon and E-Commerce Marketplaces: What Integration Requires in 2026 - Share - [Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Flocus.sh%2Fblogs%2Ftms-integration-shopify-amazon-ecommerce-marketplaces-2026%2F) - [Twitter](https://twitter.com/intent/tweet?url=https%3A%2F%2Flocus.sh%2Fblogs%2Ftms-integration-shopify-amazon-ecommerce-marketplaces-2026%2F&text=TMS%20Platforms%20That%20Integrate%20With%20Shopify%2C%20Amazon%20and%20E-Commerce%20Marketplaces%3A%20What%20Integration%20Requires%20in%202026) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Flocus.sh%2Fblogs%2Ftms-integration-shopify-amazon-ecommerce-marketplaces-2026%2F) - [Email](mailto:?subject=TMS%20Platforms%20That%20Integrate%20With%20Shopify%2C%20Amazon%20and%20E-Commerce%20Marketplaces%3A%20What%20Integration%20Requires%20in%202026&body=https%3A%2F%2Flocus.sh%2Fblogs%2Ftms-integration-shopify-amazon-ecommerce-marketplaces-2026%2F) - Print - Download - [Schedule a Demo](https://locus.sh/schedule-demo/) ### Is your team spending more time on fixing logistics plan than running the operation? - Agentic transportation management from order intake to freight settlement - Route optimization built on 250+ real-world constraints - AI-driven dispatch with automatic execution handling 20%Cost Reduction 66%Faster Planning Cycles [Schedule a demo](/schedule-demo/) Insights Worth Your Time [General](https://locus.sh/blogs/category/general/) ## [US Returns Hit $850 Billion in 2025: Why US Retailers Are Restructuring Reverse Logistics in 2026](https://locus.sh/blogs/850-billion-us-returns-ai-routing-reverse-logistics-2026/) [Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/) Last updated: Oct 29, 2026 [General](https://locus.sh/blogs/category/general/) ## [Locus 2026 UK Consumer Survey: Why Returns Visibility is Now the Conversion Engine for AI-Driven Shopping in UK Retail](https://locus.sh/blogs/returns-visibility-conversion-engine-ai-shopping-uk-retail-locus-q2-2026-consumer-survey/) [Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/) Last updated: Sep 11, 2026 [General](https://locus.sh/blogs/category/general/) ## [Locus 2026 US Consumer Survey: Generative AI isn’t Just Changing How Consumers Shop, it’s Breaking the Demand Patterns US Retail Was Built On](https://locus.sh/blogs/generative-ai-shopping-effect-retail-fulfillment-operations-locus-q2-2026-consumer-survey/) [Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/) Last updated: Jun 2, 2026 [General](https://locus.sh/blogs/category/general/) ## [Embedded vs Bolted-On AI: The Architecture Question European Logistics Buyers Are Asking](https://locus.sh/blogs/embedded-vs-bolted-on-ai-european-logistics-platform-architecture-business-benefits/) [Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/) Last updated: Jul 17, 2026 [General](https://locus.sh/blogs/category/general/) ## [Hybrid Fleet Management: How Owned, 3PL, Gig, ICE, and EV Capacity Actually Operate at Most Enterprises](https://locus.sh/blogs/three-workforce-fleet-reality-owned-3pl-gig-drivers/) [Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/) Last updated: Jul 18, 2026