Last verified: June 2026

If you've ever tried to connect Amazon Seller Central to Klaviyo, you've probably hit a wall pretty quickly. The integration that used to exist is gone. Amazon pulled it, Klaviyo deprecated it, and sellers were left piecing together workarounds. There are real, working methods in 2026 — they just require more deliberate setup than a one-click OAuth flow.

Why bother? Because Amazon keeps your customer relationships locked inside its own ecosystem. If you're running post-purchase flows, review request sequences, or abandoned checkout campaigns for your Buy with Prime storefront, Klaviyo is where that logic lives for most brands. Amazon's own retention tools don't come close. For brands managing operations across multiple channels, pairing this with a solid cross-border e-commerce stack is worth the effort.

This guide covers four methods — native app, connector tool, direct API, and manual export/import — with honest assessments of when each one makes sense. We'll also cover Amazon's communication rules, because getting the data into Klaviyo is only half the job.

Before you start

• Active Amazon Seller Central Professional account
• Admin access to your Klaviyo account
• Admin access to your Amazon Buy with Prime account (required for the native app method)
• Subscription to a connector tool like Zapier (if using that method)

Methods at a glance

Method 1: Buy with Prime native app (recommended)

This is the closest thing to a real, supported integration between Amazon and Klaviyo. The Klaviyo for Buy with Prime integration syncs order and customer data — including abandoned checkouts — directly into Klaviyo as events. It's the only method that gives you reliable customer email data, because it operates within Amazon's permitted data-sharing framework.

1. Log in to your Amazon Buy with Prime merchant console at buywithprime.amazon.com and confirm your account registration is complete. Incomplete registration is a known cause of connection failures — resolve any pending tasks before proceeding.
2. Navigate to the Integrations section within the Buy with Prime console and find the Klaviyo app listing, or go directly to the Amazon Buy with Prime Klaviyo app page.
3. Click Connect and authenticate with your Klaviyo admin credentials when prompted.
4. Authorise the data permissions — you're granting Buy with Prime permission to push order events, customer data, and abandoned checkout events to Klaviyo.
5. Select your target Klaviyo account if you manage multiple workspaces, then confirm the connection.
6. Return to Klaviyo and navigate to Integrations to verify the Buy with Prime integration shows as active.
7. Place a test order through your Buy with Prime storefront and confirm the corresponding event appears in Klaviyo's activity feed within a few minutes.

Once connected, Klaviyo receives a defined set of event types including Placed Order, Ordered Product, and Started Checkout. That's enough to build post-purchase flows, abandonment sequences, and product-specific automations. One thing to note: this integration doesn't backfill historical data. It only captures events from the moment you connect onward.

Method 2: Connector tool (e.g. Zapier)

Not on Buy with Prime? A connector platform like Zapier can bridge Amazon Seller Central order events to Klaviyo. You're working with order-level data here — don't expect customer email addresses to flow through, because Amazon's PII restrictions block that in standard Seller Central data exports. Think of this as triggering Klaviyo events based on order activity, not building a full customer profile.

1. Log in to your Zapier account and click Create Zap.
2. Set Amazon Seller Central as the trigger app and choose a trigger event — "New Order" is the most common starting point.
3. Connect your Seller Central account by entering your MWS credentials or authorising via SP-API when prompted by Zapier.
4. Test the trigger by pulling a recent order and confirming the data fields Zapier captures.
5. Add Klaviyo as the action app and select "Track Event" or "Add Subscriber to List" as the action type.
6. Map the Amazon order fields — order ID, product ASIN, fulfilment status — to the corresponding Klaviyo event properties.
7. Turn on the Zap and monitor the task history for the first few runs to confirm events are posting correctly.

A paid tier on your connector tool is required for multi-step Zaps and anything beyond basic triggers. Factor that into your stack costs. For brands thinking through their broader operations tooling, our EU expansion operations stack guide covers how connector tools fit into a larger architecture.

Method 3: Custom API integration

For high-volume sellers who want full control, building a custom integration using Amazon's Selling Partner API (SP-API) and Klaviyo's Track API is the most flexible approach. It's also the most work. Honestly, most brands underestimate the maintenance burden — Amazon API changes become your problem to fix, permanently. You're realistically looking at meaningful developer time to build, test, and keep it running, not a one-sprint job you hand off and forget.

1. Register your application in the Amazon Developer Console and request SP-API access for the relevant data roles (Orders, Notifications).
2. Set up SP-API Notifications using the Notifications API to receive push events when order status changes — this is more efficient than polling.
3. Generate a Klaviyo private API key from your Klaviyo account settings under API Keys.
4. Build your middleware service — a small application (AWS Lambda works well) that receives SP-API notification payloads and transforms them into Klaviyo Track API calls.
5. Map the event schema: order events should POST to Klaviyo's /api/events/ endpoint with properties matching your Klaviyo flow triggers.
6. Implement error handling and retry logic — API rate limits on both sides will cause dropped events without it.
7. Test end-to-end with sandbox orders before pointing at production credentials.
8. Monitor your middleware logs for the first two weeks in production to catch edge cases.

The upside is precision — you define exactly what gets sent and when. If your team already manages integrations like a Shopify to Dynamics 365 connection, the architecture will feel familiar.

Method 4: Manual CSV export/import

This isn't a real integration. But it has its place — testing Klaviyo flow logic before you've built the live connection, or running a one-off campaign against a specific order cohort.

1. Open Amazon Seller Central and navigate to Reports → Business Reports or Orders → Order Reports.
2. Generate an order report for your chosen date range and download the CSV.
3. Review the columns — note that directly identifiable customer PII (emails, full names) won't be present in standard order exports due to Amazon's data restrictions.
4. Clean the CSV to match Klaviyo's import format: at minimum you need an identifier column and any event properties you want to use.
5. Log in to Klaviyo and go to Lists & Segments → Create List → Import Contacts.
6. Upload your cleaned CSV and map columns to Klaviyo profile properties.
7. Confirm the import and spot-check a few profiles to verify the data landed correctly.

Run this more than once a month and you'll spend more time on it than any of the other methods cost to set up. Use it once, automate it next.

Common errors and how to fix them

The Klaviyo Amazon integration no longer works / data stopped syncing

The direct integration between Amazon Seller Central and Klaviyo was discontinued. Order and customer data no longer sync automatically through that legacy connection. Switch to one of the four methods above — the Buy with Prime native app is the most straightforward replacement for sellers who qualify.

Buy with Prime connection fails or won't authenticate

The most common cause is an incomplete Amazon Buy with Prime account registration. Log in to your Buy with Prime console and check for any pending tasks or verification steps flagged in your account dashboard. Resolve all outstanding items before attempting to reconnect. Also confirm you're using admin-level credentials for both platforms.

Return and cancellation events aren't appearing in Klaviyo

The Buy with Prime integration doesn't currently sync return or cancellation events to Klaviyo. If your flows depend on these triggers, you'll need to handle them through a separate mechanism — a connector tool or custom API call that listens for those specific order status changes.

No historical data after connecting Buy with Prime

The Buy with Prime integration doesn't backfill historical data. Only events that occur after the connection is established will appear in Klaviyo. If you need historical context for segmentation, a one-time manual import of order data (minus PII) is the only workaround.

Customer emails missing from synced data

Amazon's PII policy prevents standard Seller Central data exports from including customer email addresses for use in marketing platforms. The Buy with Prime integration is the exception — it provides more complete customer profile data within Amazon's permitted framework. Standard connector tool integrations pulling from Seller Central order reports won't include emails.

Frequently Asked Questions

Can you connect Amazon Seller Central to Klaviyo?

Not directly — Amazon deprecated the native Klaviyo integration for Seller Central. You can connect the two platforms using Amazon's Buy with Prime app (if you use that programme), a connector tool like Zapier, or a custom API build. Each method has different data access and setup requirements.

How do I import Amazon contacts into Klaviyo?

Amazon's PII policy prevents sellers from exporting customer contact lists — including email addresses — for bulk import into marketing platforms. You can import order-level data (ASINs, order IDs, fulfilment status) via CSV, but customer emails are restricted. The Buy with Prime integration is the only supported path to getting customer email data into Klaviyo from Amazon.

How do I automate review requests for Amazon orders?

Amazon's Communication Guidelines permit proactive messages requesting product reviews or seller feedback. You can trigger a Klaviyo flow on the Placed Order event from your Buy with Prime integration and send a post-purchase review request — but the message must comply with Amazon's rules. No promotional content, no external links, and the request must relate to the specific order.

Does Klaviyo have an Amazon integration?

Klaviyo has a supported integration specifically with Amazon's Buy with Prime programme, which syncs order events, customer data, and abandoned checkout data. There's no direct integration with standard Amazon Seller Central — that connection was discontinued. Sellers not on Buy with Prime need a third-party connector or a custom API solution.

Amazon's communication policies: what you can and can't do

Here's the part most brands skim and later regret. Amazon takes communication violations seriously — account suspension is a real outcome, not a theoretical one. Worth understanding before you build a single flow.

Amazon's Communication Guidelines permit proactive messages for a narrow set of purposes: completing the order, requesting reviews or feedback, or providing essential order information. Marketing and promotional content — including coupons or discount codes — is not permitted in messages to Amazon customers. Directing customers away from Amazon via external links is also forbidden, unless those links are strictly necessary to complete the order.

And then there's the PII angle. Amazon's data policy restricts storage of customer personally identifiable information. According to Amazon's SP-API data protection policy, PII obtained through the Buy with Prime integration or SP-API may only be retained for as long as needed to fulfil the order, with a 30-day post-fulfilment window in most cases (verify the current version of Amazon's data protection requirements directly, as these terms are updated periodically). In practice, your Klaviyo flows need explicit suppression logic to stop contacting customers once that window closes — don't assume the integration handles this for you.

Keep your Amazon-triggered Klaviyo flows transactional or review-focused. Not promotional. Tightly scoped. If you're building out a broader post-purchase architecture for a multi-channel brand, the sustainable fulfilment tech stack guide covers how these data flows fit into the wider picture. And for brands managing Amazon alongside other sales channels, pairing this with good customer support tooling — see our guide on how to connect Gorgias to Amazon — ties together the post-purchase side without running afoul of messaging rules.

One last thing: Amazon data should not be used to build retargeting audiences or seed lookalike lists on ad platforms. That's outside the permitted use case for data obtained through the Buy with Prime integration or SP-API.

If you're already on Buy with Prime, the native app is the clear answer — lower maintenance, supported by both platforms, and the only path to reliable customer email data. On standard Seller Central and want order-event triggers without writing code? A connector tool gets you there with moderate setup. Custom API is for teams with developer resource who need precise control at volume. Manual CSV import is fine for a single test run — automate it as soon as you can. The decision mostly comes down to your technical capacity and how central Klaviyo is to your retention stack.

Last verified: June 2026

Think about what fast fashion actually demands operationally: production runs that last days, trend signals you need to catch before they peak, SKU turnover that would exhaust most mid-market brands' entire planning cycle. Every layer of your stack has to talk to every other layer. Nothing can create friction between a trend spike and a shipped order. A basic Shopify-plus-email setup simply isn't enough.

This article covers the full fast fashion tech stack: storefront, email, customer support, reviews and loyalty, returns, analytics, paid advertising, and a compliance layer — because if you're selling into EU markets, Refashion and the broader EU textile compliance picture will catch up with you whether you're ready or not. The stack is built for brands doing somewhere between 500 and 10,000 orders a month, operating on one or more marketplaces, with a small ops team wearing multiple hats.

One thing worth saying upfront: the fastest operators in this category have production loops of around five days. Your tech stack won't manufacture clothes faster. But it can absolutely eliminate the operational drag that slows everything else down.

E-commerce platform

Your storefront is the foundation everything else plugs into. In fast fashion, that means you need a platform that handles rapid SKU turnover, flexible merchandising, and international selling — without calling a developer every time you want to push a new drop.

Shopify

Shopify is the default choice for most fast fashion DTC brands, and it deserves that reputation. It's genuinely fast to launch on, has the deepest app ecosystem of any e-commerce platform, and its multi-channel selling (Meta, TikTok, Pinterest, Google) is built in rather than bolted on. For a brand pushing new collections weekly, the ability to spin up product pages, activate abandoned cart flows, and connect to social channels from a single dashboard matters more than you'd expect.

Strengths

• Drag-and-drop store builder with theme customisation — useful when you're refreshing storefronts around seasonal drops
• Shopify Markets for multi-currency and multilingual selling, which becomes relevant as soon as you start expanding into the EU or US
• 8,000+ apps in the Shopify App Store, covering almost every operational need in this stack

Best fit

Ideal for DTC fashion brands on one or two channels who want fast time-to-market and minimal technical overhead. More detailed reporting — sales by channel, product, or customer cohort — requires a higher-tier plan.

BigCommerce

BigCommerce is worth knowing about, particularly if you're running a more complex operation — multiple storefronts, B2B wholesale alongside DTC, or a headless architecture where you want your front-end and back-end separated. Less plug-and-play than Shopify, but more configurable out of the box for businesses that have outgrown simple setups. If you're running a wholesale or trade account alongside your consumer store, the native B2B features (customer groups, bulk pricing, quote management) save real development time.

Strengths

• Multi-storefront management from a single back-end — useful if you run separate branded stores for different lines
• Open API and headless commerce support for brands that want custom front-end experiences
• Native B2B capabilities without needing a separate app

Best fit

Better suited to fast fashion brands with complex catalogue needs, multiple storefronts, or a wholesale component. Annual sales limits apply by plan tier, which may force an upgrade at scale.

Email marketing

Email is still the highest-ROI owned channel in e-commerce. In fast fashion, it does double duty: new drop announcements and back-in-stock alerts drive immediate revenue, while automated flows — welcome series, browse abandonment, win-back — keep the retention engine running in the background.

Klaviyo

Klaviyo is the dominant email and SMS platform in the Shopify ecosystem. Its strength in fast fashion specifically is the segmentation engine — you can build audiences based on purchase behaviour, browsing patterns, predicted lifetime value, and channel engagement, then fire targeted flows for new drops or limited restocks. The integration with Gorgias, Loop Returns, and Yotpo (all in this stack) means customer data flows in multiple directions rather than sitting in silos. If you're on BigCommerce or WooCommerce, the integration exists there too.

Strengths

• Unified customer profiles pulling in purchase, browse, and engagement data for precise segmentation
• Automated flows for drop launches, restocks, browse abandonment, and win-back campaigns
• Predictive analytics to identify high-value customers before they churn

Best fit

The go-to for fashion brands with growing lists and a need for granular segmentation. The free plan covers 250 active profiles and 500 email sends per month — useful for testing, but you'll move off it quickly.

Mailchimp

Mailchimp is a reasonable starting point for early-stage brands that need basic campaign and automation capabilities without the complexity of a specialist e-commerce platform. It handles campaign creation, automation workflows, audience segmentation, and landing pages well enough, and integrates with Shopify. But be clear about the trade-off: once you're running multiple product lines, complex flows, or SMS alongside email, Klaviyo's e-commerce focus becomes meaningfully better.

Strengths

• Straightforward campaign builder that non-technical founders can use without training
• Marketing automation workflows for standard e-commerce triggers
• Free tier available for brands just getting started

Best fit

Best for fashion startups at very early stage who want to keep the stack simple. All contacts — including unsubscribed ones — count toward your plan limit unless actively archived or deleted.

Customer support

Fashion customer support is mostly returns and sizing queries. Hundreds of them, daily, asking the same five things. Slow responses translate directly into negative reviews, and high ticket volume with a small team means you need automation doing real work, not just sorting inboxes. The right tool here handles routine queries without an agent touching them, and gives agents full order context when a query does need a human — no tab-switching, no copy-pasting order numbers.

Gorgias

Gorgias is built specifically for e-commerce, which makes it the natural fit here. The Shopify integration is deep — agents can view order details, issue refunds, apply discounts, and edit orders without leaving the conversation thread. For a fast fashion brand handling hundreds of "where's my order" and "can I exchange for a different size" tickets daily, that in-conversation action capability cuts handle time substantially. The AI Agent resolves a meaningful share of routine tickets automatically. And if you're also selling on Amazon, connecting Gorgias to Amazon Seller Central is worth setting up early.

Strengths

• Native Shopify integration with in-conversation order actions (cancel, refund, discount, edit) — no tab-switching
• Omnichannel inbox covering email, chat, SMS, WhatsApp, Instagram, and Facebook in one place
• Revenue attribution reporting so you can see which support interactions actually convert

Best fit

The right call for Shopify-first fashion brands with meaningful ticket volume. The AI Agent is an add-on billed per resolved conversation, separately from the helpdesk subscription — factor that into your cost model if you're planning to lean on it heavily.

Zendesk

Zendesk is the enterprise standard in customer support software. Omnichannel ticketing, a mature self-service knowledge base, AI-powered automation, workforce management tools — it's all there. For a fast fashion brand at scale — 50+ support agents, multiple brands under one umbrella, complex SLA requirements — it makes sense. For a 10-person brand, it's probably more infrastructure than you need.

Strengths

• Omnichannel ticketing across email, chat, phone, social, and messaging apps
• Self-service Help Centre that deflects repetitive queries before they hit the queue
• Zendesk Explore for detailed reporting and performance analytics

Best fit

Better suited to larger fashion operations or multi-brand groups that need enterprise-grade support infrastructure. Advanced AI features and certain add-ons are locked behind higher tiers or carry additional costs.

Customer reviews and loyalty

Acquiring a new customer in fashion is expensive. Keeping one is where the economics actually work. That means reviews, loyalty programmes, and referral mechanics aren't optional extras — they're the retention engine. And in a category where customers buy with their eyes, photo and video UGC from real customers does more conversion work than any product shot you commission.

Yotpo

Yotpo combines reviews, loyalty, and SMS marketing in one platform — useful if you want to reduce tool count. The photo and video review capability is particularly valuable in fashion: UGC showing real customers wearing your products converts better than product shots alone. The AI-powered review summaries and sentiment analysis give you a genuine feedback signal for which styles are landing and which aren't, which feeds back into production decisions. The Klaviyo integration means you can trigger email and SMS flows based on review submission or loyalty point milestones.

Strengths

• Photo and video review collection via email, SMS, and AI prompts — strong for fashion UGC
• Loyalty and referral programmes including VIP tiers and custom rewards
• AI-powered review summaries and sentiment analysis for product feedback loops

Best fit

Well suited to fashion brands wanting a combined reviews-plus-loyalty solution in one tool. The Starter Reviews tier is limited to 500 orders per month — growing brands will need to move up.

LoyaltyLion

LoyaltyLion is a dedicated loyalty platform rather than a bundled suite, which means it goes deeper on programme mechanics than most. VIP tiers, points for purchases and reviews and referrals, "buy with points" redemption, and AI-recommended bonus campaigns give you real flexibility in designing a loyalty programme that fits your brand. The Klaviyo and Yotpo integrations mean loyalty data flows into your email flows and review requests. If loyalty is a core pillar of your retention strategy rather than a nice-to-have, this is worth having as a standalone rather than the loyalty module inside a broader tool.

Strengths

• Flexible rewards structure covering purchases, reviews, referrals, birthdays, and custom on-site activities
• VIP tiers and "Buy With Points" redemption on higher plans
• AI-powered features including recommended rewards and bonus campaigns

Best fit

A strong choice for mid-market fashion brands where loyalty is a key retention lever. The free tier supports up to 400 monthly orders — meaningful for early validation, but most growing brands will need a paid plan.

Returns management

Returns are a fact of life in fashion, especially online. Sizing variability and photography that doesn't always match real-world colour and texture mean a meaningful percentage of orders come back. Convert as many as possible into exchanges. Process the rest without burning your support team's time. Virtual try-on technology is helping here (brands using it report return rate reductions of up to 48%), but the returns infrastructure still matters for everything that does come back.

Loop Returns

Loop Returns is built with an exchange-first philosophy, which aligns well with fast fashion economics. Rather than defaulting customers to a refund, Loop's self-service portal presents exchanges and Shop Now options first — keeping the revenue in the business. Instant Exchanges let customers get a replacement before sending the original back, which reduces the friction that often pushes customers toward a refund instead. Fraud detection is built in on the Advanced plan, which matters for higher-volume fashion brands who see systematic return abuse.

Strengths

• Exchange-first return flow with Shop Now and Instant Exchange — designed to retain revenue rather than refund it
• Self-service returns portal with automated policy enforcement and workflows
• Native integrations with Gorgias and Klaviyo for a connected post-purchase experience

Best fit

The right choice for Shopify fashion brands with meaningful return volumes who want to convert returns into exchanges. Order Tracking pricing is based on plan and monthly shipment volume, with a per-shipment fee for volumes above the monthly estimate.

AfterShip

AfterShip covers both shipment tracking and returns management, making it a viable single tool for post-purchase if you want to simplify the stack. The branded tracking pages with product recommendations turn a "where's my order" page into a retention touchpoint — which most fashion brands underuse. AfterShip's fit within a circular economy-oriented stack is also worth noting if sustainability positioning matters to your brand.

Strengths

• Shipment tracking across more than 1,200 carriers with AI-powered estimated delivery dates
• Branded tracking pages with personalised product recommendations
• Automated returns management with exchange-first options

Best fit

Good for brands that want tracking and returns in one tool without managing two separate platforms. The free shipping plan covers 10 labels per month — a testing tier, not an operational one.

Analytics

Here's the thing most brands miss: in fast fashion, analytics aren't a reporting function. They're an operational input. Which products gained traction in the first 48 hours of a drop? Where are users abandoning a product page? Which traffic sources are actually converting? You need quantitative data (traffic, conversions, revenue) alongside behavioural data (heatmaps, session replays, direct user feedback) — because the numbers tell you what's happening, and the recordings show you why.

Google Analytics

Google Analytics 4 is the baseline for traffic and conversion measurement. It's free, it integrates with Google Ads and the rest of the Google stack, and its e-commerce analytics cover conversion tracking, funnel analysis, and audience behaviour well enough for most brands. The AI-powered predictive metrics are genuinely useful for identifying customers likely to churn or convert, which feeds into Klaviyo segmentation. For brands doing high volumes: the free tier limits data retention to 14 months and applies sampling at high traffic volumes.

Strengths

• Conversion tracking and e-commerce analytics with funnel and path exploration
• AI-powered predictive metrics and anomaly detection
• Deep integration with Google Ads, Tag Manager, and BigQuery for advanced analysis

Best fit

Essential infrastructure for any e-commerce brand — there's no real reason not to have it running. The free GA4 plan limits data retention to 14 months and employs sampling for high traffic volumes; the enterprise tier (GA360) is priced for large organisations.

Hotjar

Hotjar fills the gap that quantitative analytics can't — it shows you what users are actually doing on your pages. Heatmaps reveal which parts of a product page get attention and which get ignored. Session replays let you watch real users hesitate, scroll back, and abandon carts. For a fashion brand, this is how you find out that your size guide is being ignored, or that mobile users can't easily see the colour swatch selector. The on-site surveys add a qualitative layer — asking users directly why they didn't buy is often more informative than inferring it from click data.

Strengths

• Heatmaps and session replays to understand where users engage and where they drop off
• On-site surveys and feedback tools for direct user input
• Funnel analysis to identify conversion blockers at a page-by-page level

Best fit

A useful complement to GA4 for any brand actively optimising product pages and checkout flows. Free tier available — worth pairing with GA4 rather than treating as an either/or.

PPC management

Campaign structures that worked last season are often irrelevant this one. Budgets need to follow product trends in near real-time, and manually managing Google Shopping, Meta, Amazon Ads, and Microsoft Ads across a high-SKU catalogue is genuinely unsustainable past a certain volume. These tools automate the repetitive optimisation work — bid management, budget pacing, anomaly alerts — so your team can spend time on decisions that actually require judgment.

Optmyzr

Optmyzr is a PPC management platform for in-house paid search teams and agencies managing campaigns across multiple platforms simultaneously. The one-click optimisation features and real-time campaign monitoring cut the manual work of bid management and budget allocation. For a fast fashion brand running Google Shopping campaigns across a high-SKU catalogue, the shopping campaign management tools in particular save significant time. Alerts push to Slack and Microsoft Teams, so you don't need to log into another dashboard to catch problems.

Strengths

• User-controlled automation for bid management and budget pacing across Google Ads, Microsoft Ads, and Meta Ads
• Shopping campaign management tools suited to high-SKU fashion catalogues
• Advanced reporting and dashboards with real-time monitoring

Best fit

Well suited to fashion brands or their agencies managing PPC across multiple ad platforms with a need to automate repetitive optimisation tasks. API access is available on the Enterprise plan only.

SellerApp

SellerApp is specifically focused on Amazon — the right tool if you're running Amazon PPC alongside your DTC store, which many fast fashion brands do when scaling. Product research, keyword optimisation, listing quality analysis, and PPC automation for Amazon Seller Central are its core functions. It's more narrowly scoped than Optmyzr, but if Amazon is a meaningful revenue channel, that focus is an advantage rather than a limitation. For brands tracking Amazon inventory alongside Shopify, pairing SellerApp with a proper IMS creates a much cleaner picture — see our guide to syncing Amazon FBA inventory for the basics.

Strengths

• Amazon-specific PPC management and advertising automation
• Keyword research and listing optimisation tools for Amazon catalogue management
• Profit dashboard and sales data analysis for Amazon performance tracking

Best fit

The right choice for fashion brands where Amazon is a primary or growing channel. The freemium plan covers 2 products and 10 searches per day — functional for evaluation, not for active management.

Inventory and compliance

Honestly, this is the category most fast fashion brands underinvest in — and it's always obvious in hindsight. An oversell kills a viral moment. A stockout mid-campaign hands customers to a competitor. A compliance notice from a French regulator lands and nobody on the team knows what Refashion even is. We've watched brands waste entire quarters sorting out infrastructure problems that could have been resolved in a week with the right tooling in place.

For EU-selling fashion brands, textile EPR obligations under Refashion (France) and UPV (Netherlands) are live compliance requirements now, not future considerations. The EU expansion stack covers the broader picture, but the short version is: sort it before your next French campaign. Retrofitting compliance after the fact is significantly more painful than building it in from the start.

Ceendesis

Ceendesis combines multi-channel inventory management, EPR compliance (including textile EPR for fashion brands), and marketplace-to-accounting sync in one platform. For a fast fashion brand selling across Shopify and Amazon — and potentially eBay, Walmart, or TikTok Shop — having inventory, compliance reporting, and financial reconciliation in one place removes a significant amount of operational overhead. The native Xero and QuickBooks integrations mean marketplace payouts reconcile automatically rather than requiring manual work or a separate connector. If you're working through how to reconcile Shopify payouts in Xero or connect Amazon Seller Central to QuickBooks, Ceendesis handles both natively.

Strengths

• Combines multi-channel inventory, EPR compliance, and marketplace-to-accounting sync in one platform
• Built for brands selling on Shopify, Amazon, eBay, Walmart, and TikTok Shop
• Native Xero and QuickBooks reconciliation for marketplace payouts

Best fit

Built for brands on 2+ marketplaces — overkill for single-channel Shopify-only stores.

The stack at a glance

Frequently asked questions

What software do fast fashion brands use?

Fast fashion brands typically run a combination of PLM (Product Lifecycle Management) software for design and development, inventory management systems for real-time stock visibility across channels, e-commerce platforms like Shopify for DTC sales, and AI-powered tools for trend forecasting and demand planning. On the marketing side, email automation (Klaviyo being the most common in e-commerce), loyalty platforms, and returns management tools round out the core stack. Brands like Zara, H&M, and Forever 21 have long used PLM as a backbone for managing high-volume design cycles — but the tooling is increasingly accessible to mid-market brands too.

How do you manage inventory for on-demand clothing?

On-demand and fast fashion inventory management comes down to two things: real-time stock visibility across every sales channel, and just-in-time (JIT) replenishment to avoid holding excess stock. JIT minimises inventory holding costs by ordering or producing only when demand is confirmed — Zara built much of its competitive model on this. In practice, that means a centralised inventory system that syncs stock across your Shopify store, any marketplaces, and your warehouse in real time, paired with demand forecasting to avoid both stockouts and overstock situations. For brands on multiple channels, this is where a proper multi-channel IMS pays for itself quickly.

What is a PLM system in fashion?

Fashion PLM (Product Lifecycle Management) centralises product data, workflows, and collaboration across the entire collection lifecycle — from initial concept and sourcing decisions through to production sign-off and retail delivery. The value is primarily about eliminating version-control chaos: one system of record for tech packs, material specifications, costing sheets, and supplier communications, accessible to every stakeholder simultaneously. For fast fashion brands running multiple collections with short lead times, PLM is the difference between a controlled development process and a chaotic one. It's a separate tool category from IMS — PLM manages the product before it exists; IMS manages it once it does.

How is AI changing fashion operations in 2026?

AI has moved from pilot projects to core operational infrastructure in fashion. According to data cited

Screenshots are from each tool's public pricing or features page, captured June 2026. We are not affiliated with any third-party tool listed unless explicitly noted.

Last verified: June 2026

Stripe powers payments for a huge slice of e-commerce. It's fast, developer-friendly, and globally accepted. But connecting it cleanly to QuickBooks Online? That's where things get messy.

The problem is structural. Stripe deposits a net amount into your bank — gross revenue minus processing fees, refunds, and any other deductions — and that single lump-sum deposit needs to reconcile to a pile of individual transactions in QuickBooks. Get that wrong and your P&L is fiction.

The good news: there's a clear path forward. Multiple paths, actually, each suited to different volumes and team sizes. Whether you're processing a handful of Stripe payments a week or running a high-volume store where Stripe, Shopify Payments, and Amazon settlements all need to land cleanly in the same ledger (if so, see our guide on connecting Amazon Seller Central to QuickBooks), there's a method here that fits.

This guide covers every method: the native connector, a third-party connector tool, the manual CSV route, and the managed option via Ceendesis Accounting. We'll walk through each step by step, flag the common failure points, and tell you plainly which method to pick for your situation.

Before you start

• Active Stripe account
• Active QuickBooks Online account

Methods at a glance

Method 1: Native app — Stripe Connector by QuickBooks

The Stripe Connector by QuickBooks is a direct integration built by Intuit that pulls Stripe transactions into QuickBooks automatically. It's free for QuickBooks Online customers and takes about 20 minutes to configure.

That said, it has real limitations. It doesn't separate Stripe fees from gross sales, doesn't handle refunds cleanly, and doesn't generate the journal entries you'd need to reconcile net payouts to individual transactions. For a store doing a few dozen transactions a month with straightforward pricing, it's fine. For anything more complex, you'll feel those gaps quickly.

1. Open the QuickBooks App Store and search for "Stripe Connector by QuickBooks". Click Get app now.
   Expected result: You're redirected to an authorisation screen.
2. Authorise your QuickBooks Online account by signing in when prompted.
   Expected result: The app confirms it's connected to your QBO company file.
3. Connect your Stripe account by clicking Connect with Stripe and completing the OAuth flow in Stripe's interface.
   Expected result: The connector shows your Stripe account as linked. If you have multiple Stripe accounts, confirm you've selected the right one.
4. Set your sync start date — choose the date from which you want transactions imported. Don't set this earlier than your QuickBooks start date or you'll create duplicate entries for any period you've already manually reconciled.
   Expected result: The connector displays a confirmation of your chosen date range.
5. Map your Stripe income to a QuickBooks income account in the settings panel. If you haven't already, create a dedicated Stripe Fees expense account in QuickBooks (Chart of Accounts → New → Expense). Mapping fees to a dedicated account is critical for accurate P&L reporting.
   Expected result: Income and fee categories are mapped; the connector is ready to sync.
6. Run the initial sync by clicking Sync now.
   Expected result: Stripe transactions appear in your QuickBooks Banking tab under the connected account, ready for review and matching.

Method 2: Connector tool (third-party)

As transaction volume grows or your accounting setup gets more sophisticated — multiple currencies, subscription billing, high refund rates — the native connector starts to creak.

Third-party connector tools are built specifically for these scenarios. They typically implement the clearing account pattern automatically: gross revenue posts to your income account, processing fees post to a dedicated expense account, and the net payout matches to your bank feed. That structure is the accepted best practice for accurate Stripe reconciliation. These tools require a paid subscription, though free tiers are sometimes available for low volumes. Check the vendor's current pricing before committing — don't rely on anything quoted here.

1. Choose your connector tool and create an account. Look for one that explicitly supports a clearing account / journal entry model for Stripe payouts, handles refunds as separate line items, and lets you set your own timezone to avoid UTC mismatches.
   Expected result: You have an active account with your chosen tool.
2. Connect your Stripe account inside the tool using the OAuth flow it provides. Grant read access to transactions, payouts, and fees.
   Expected result: The tool shows your Stripe account status as connected and begins retrieving historical data.
3. Connect your QuickBooks Online account via the tool's QBO integration. Authorise it to create transactions in your company file.
   Expected result: Both platforms show as connected in the tool's dashboard.
4. Configure your account mapping: assign Stripe gross sales to an income account, Stripe fees to your dedicated expense account, and refunds to either a contra-revenue or separate expense account depending on your accountant's preference. Set a Stripe clearing account as the intermediary.
   Expected result: The mapping screen shows all transaction types assigned to specific QuickBooks accounts.
5. Set your timezone in the tool's settings to match QuickBooks' local time setting. Stripe exports use UTC by default; if your QBO company is set to US Eastern or UK time, a mismatch here will scatter transactions across the wrong accounting periods.
   Expected result: Transaction dates in the tool preview match the dates you'd expect in QuickBooks.
6. Run a test sync for a short historical period (one week works well). Review the resulting transactions in QuickBooks and confirm that gross revenue, fees, and net payouts all appear as separate line items.
   Expected result: Your clearing account shows a zero or near-zero balance after the payout matches the bank feed — that's the sign everything's working correctly.
7. Enable automatic syncing and set the sync frequency. Daily is sufficient for most stores; hourly is available in most paid tiers if you need near real-time visibility.
   Expected result: The tool runs on schedule without manual intervention.

Method 3: Manual export/import (CSV)

This is the no-tools option. It works, but it doesn't scale — each reconciliation period means repeating the full process from scratch. If you're doing a one-off historical catch-up, clearing a backlog before switching to an automated method, or genuinely processing fewer than a couple of dozen transactions a month, manual CSV is viable. For anything busier, the time cost adds up fast.

1. Log in to your Stripe Dashboard and go to Payments → All transactions. Click Export and select the date range you want to reconcile. Choose CSV format and include the columns for amount, fee, net, and payout date.
   Expected result: A CSV file downloads to your machine.
2. Open the CSV and review it before importing. Check that the date format is consistent and note that Stripe timestamps are in UTC — if your QuickBooks company uses a different timezone, adjust the dates in the file before importing to avoid posting transactions to the wrong period.
   Expected result: Your CSV has clean, consistent dates and no formatting anomalies.
3. Log in to QuickBooks Online and go to Banking → Upload transactions. Select your Stripe clearing account (create one first if it doesn't exist — Chart of Accounts → New → Bank account, name it "Stripe Clearing").
   Expected result: QBO's import wizard loads.
4. Map the CSV columns to QBO fields: Date, Description, Amount. QuickBooks will ask you to confirm which column maps to which field.
   Expected result: The preview shows transactions correctly formatted before you confirm the import.
5. Complete the import and go to the Banking tab. Match the imported Stripe transactions to your actual bank deposits. For each Stripe payout, create a journal entry that debits the Stripe clearing account and credits your bank account for the net payout amount.
   Expected result: The clearing account balance returns to zero; the bank account reflects the correct net deposit.
6. Record Stripe fees separately by creating expense transactions from the fee column in your CSV, posted to your Stripe Fees expense account.
   Expected result: Your P&L shows processing fees as a distinct line item, not hidden inside revenue.

Method 4: Ceendesis Accounting

Ceendesis Accounting is the managed option — the reconciliation setup, ongoing syncing, and account mapping are all handled for you. It's particularly useful when Stripe isn't your only payout channel: Ceendesis reconciles Amazon, Shopify, Walmart, and eBay settlements into QuickBooks and Xero alongside Stripe, with per-channel COGS tracking and a full settlement flat-file parser for Amazon's SP-API.

Worth knowing upfront: Ceendesis currently supports QuickBooks and Xero — no Sage integration yet. If you're on Sage, Methods 1–3 are your routes.

1. Contact the Ceendesis team at ceendesis.com/accounting to start onboarding. You'll be asked about your channel mix, transaction volumes, and current QuickBooks setup.
   Expected result: You receive a scoping confirmation and onboarding timeline.
2. Grant Stripe API access by providing a restricted API key with read permissions for charges, payouts, and refunds. Ceendesis will specify the exact permission set needed.
   Expected result: Ceendesis confirms Stripe data is accessible and the historical import scope is agreed.
3. Connect your QuickBooks Online account via the OAuth flow Ceendesis provides during onboarding.
   Expected result: Both connections are confirmed active in your Ceendesis dashboard.
4. Review the proposed account mapping — Ceendesis will present a draft mapping for gross revenue, processing fees, refunds, and net payouts against your existing QuickBooks chart of accounts. Approve or adjust in consultation with your accountant.
   Expected result: The agreed mapping is locked in; the clearing account structure is configured.
5. Approve the initial historical sync for your chosen backfill period. Ceendesis runs this and flags any anomalies for your review before finalising.
   Expected result: Historical Stripe transactions appear in QuickBooks correctly categorised; clearing account balances to zero.
6. Go live on automated syncing — from this point, Stripe payouts sync to QuickBooks on a regular cadence without manual input.
   Expected result: Your QuickBooks bank feed stays current; fees, refunds, and gross revenue reconcile to net payouts automatically.

Common errors and how to fix them

Net deposit doesn't match gross revenue in QuickBooks

This is the classic Stripe accounting problem. Stripe deposits a net amount — gross revenue minus fees and refunds — but your bank feed shows that net figure, not the original sale amounts. The fix is the clearing account pattern: post gross sales to your income account, fees to an expense account, and use the clearing account as the intermediary that settles to zero when the payout hits your bank. If you set this up correctly, the maths works out. If you skipped it and recorded the net deposit directly as revenue, your income is understated by every fee you've ever paid.

Transactions posting to the wrong date

Stripe exports use UTC timestamps. If your QuickBooks company is set to US Eastern or Pacific time, a Stripe transaction processed at 11pm ET will appear in Stripe's export as the following day. Multiply that across a month-end and you've got transactions bleeding between accounting periods. Fix this by adjusting your export timezone in Stripe's dashboard settings before pulling reports, or configure your connector tool's timezone setting to match QuickBooks' local time.

Lump-sum payout won't match individual transactions

Stripe bundles multiple transactions into a single payout — sometimes covering several days of sales. Trying to match that one deposit to one invoice in QuickBooks won't work; it'll never balance. The correct approach is to match the payout to the clearing account balance, not to individual transactions. Each transaction posts to the clearing account on its sale date; the payout sweeps the clearing account to zero when it lands in your bank. If you're using the native connector and it's not creating clearing account entries, you'll need to manage this step manually or switch to a connector tool that handles it automatically.

Duplicate or garbled transactions from a connector tool

Some connector tools import transactions in formats that QBO doesn't handle cleanly — creating duplicates, splitting single transactions into multiple line items, or importing metadata fields as transaction descriptions. Before enabling automatic syncing with any third-party tool, always run a test sync against a small historical window and review every imported transaction in QuickBooks. If you see duplicates, check whether the tool and the native connector are both active — running two integrations simultaneously is a common cause.

Frequently asked questions

How do I sync Stripe with QuickBooks Online?

The quickest route is the Stripe Connector by QuickBooks, available free from the QuickBooks App Store. Install it, authorise both accounts via OAuth, set your sync start date, and map your income and fee accounts. For higher volumes or more complex reconciliation, a third-party connector tool or a managed service like Ceendesis Accounting gives you better fee separation and payout matching.

Does Stripe integrate directly with QuickBooks Online?

Yes — Intuit built and maintains a native Stripe connector that connects directly to QuickBooks Online. It's free for QBO customers. The direct integration covers basic transaction syncing but has known limitations around fee separation, refund handling, and high-volume reconciliation.

How do I account for Stripe fees in QuickBooks Online?

Create a dedicated expense account in QuickBooks (Chart of Accounts → New → Expense, name it "Stripe Processing Fees" or similar). Then map all Stripe fee transactions to that account — either through your connector tool's settings or manually when importing CSVs. Keeping fees in their own account means your P&L shows the true cost of payment processing as a distinct line item, not buried in revenue.

How do I reconcile Stripe payouts in QuickBooks?

Use a Stripe clearing account as an intermediary. Gross sales post to your income account and debit the clearing account on the transaction date; when the payout hits your bank, it credits the clearing account for the net amount and debits your bank account. The clearing account should net to zero after each payout cycle. This approach — sometimes called the clearing account method — is the accepted best practice for accurate Stripe reconciliation and handles the gross vs. net mismatch that causes most errors. For more on reconciling marketplace payouts, our guide on reconciling Shopify payouts in Xero covers the same pattern applied to a different channel.

Which method should you pick?

Here's the honest summary.

If you're a low-volume store — say, under a hundred Stripe transactions a month — the free native connector is a reasonable starting point. Understand its limitations going in (no clean fee separation, no clearing account entries) and supplement with manual journal entries if needed.

If your volume is higher, your pricing is complex, or you're dealing with subscriptions and frequent refunds, a third-party connector tool that implements the clearing account pattern automatically will save you hours of monthly reconciliation work.

Manual CSV import is only worth it for historical catch-up work or very occasional use. The ongoing time cost is real — don't let it become a monthly ritual.

And if Stripe is one of several payout channels you're managing — alongside Amazon settlements, Shopify payouts, or others — Ceendesis Accounting handles all of them in one place, reconciling into QuickBooks or Xero without requiring you to run separate integrations per channel. That's where the managed approach earns its keep. For a broader view of how payment and operations tools fit together, our cross-border stack for US e-commerce is worth a read too.

Last verified: June 2026

Selling into the US from abroad — or pushing a US brand into new international markets — is genuinely complex. Not "skim a blog post and crack on" complex. We're talking multiple tax jurisdictions, customs documentation, currency conversion, consumer expectations around two-day delivery, and return flows that span continents. The brands that handle it well don't do it manually. They build a stack.

This article is for e-commerce operators who are either a foreign brand entering the US market, a US brand starting to ship internationally, or somewhere in between — scaling past the point where cobbling things together still works. We've mapped out the six functional layers you need and matched a tool to each, based on what they actually do rather than what their marketing claims.

One thing upfront: cross-border operations touch compliance territory that goes well beyond this stack. If you're selling into EU markets — whether that's packaging, textiles, or battery-containing products — there's a whole separate compliance layer on top of what's covered here. We've written about that in our EU expansion operations stack. For now, let's focus on the US-facing cross-border stack.

E-commerce platforms

Your platform is the foundation everything else connects to. For cross-border specifically, you need one that handles multi-currency pricing, international checkout, and plays well with the tax, fulfilment, and localisation tools sitting downstream. Switching platforms mid-growth is painful, so get this right early.

Shopify

Shopify is the dominant cloud-based e-commerce platform for SMEs and growing brands. Its cross-border credentials have improved significantly with Shopify Markets — the built-in feature that handles multi-currency pricing, local domains, and language switching without requiring a separate app for each.

Strengths

• Shopify Markets enables multi-currency and multilingual selling from a single store, with local payment method support and regional pricing rules.
• The Shopify App Store connects to 8,000+ third-party tools — meaning every other tool in this stack (Zonos, ShipBob, Loop Returns, Weglot) integrates directly.
• Automated tax calculation and abandoned cart recovery are included out of the box, reducing the baseline ops lift for new market entry.

Best fit

Best for brands that want a broad ecosystem and fast international setup without heavy dev work. Note that higher-tier plans are required to unlock more detailed reports — sales by channel, product, staff, location, and customer cohort analysis.

BigCommerce

BigCommerce is a scalable platform built for growing and enterprise-level businesses, with stronger native B2B capabilities than Shopify and an open API that makes custom headless builds more accessible.

Strengths

• Multi-storefront management lets you run region-specific storefronts (US, EU, APAC) from a single back-end — useful once you're operating across multiple markets at scale.
• Native B2B capabilities — customer groups, bulk pricing, quote management — are built in, not bolted on via apps. That matters for brands with wholesale or distributor channels alongside DTC.
• Deep ERP and CRM integrations (Oracle NetSuite, Microsoft Dynamics 365, Salesforce) make BigCommerce a reasonable choice if you're connecting to enterprise back-office systems. We've written a related guide on the Shopify-to-Dynamics 365 integration if you're evaluating that route instead.

Best fit

Good fit for mid-market and enterprise brands with B2B requirements or complex multi-storefront needs. Annual sales limits apply per plan, so you may need to upgrade if you grow quickly.

International payments

Payment infrastructure for cross-border selling has two jobs: accepting the widest possible range of payment methods globally, and moving money reliably across currencies. You probably need both tools here — they serve different buyer segments and geographies.

Stripe

Stripe is the developer-first payment processor that's become the default infrastructure for e-commerce brands building international payment flows — partly because its API coverage is exceptional, and partly because Stripe Tax handles automated VAT, GST, and sales tax calculation in one product.

Strengths

• Stripe Tax automates sales tax, VAT, and GST calculation across jurisdictions — directly relevant for US economic nexus compliance (more on that in the Tax & Duty section).
• Stripe Radar provides fraud detection and risk management, which matters more for cross-border transactions where fraud rates are typically higher than domestic ones.
• Subscription and recurring billing management is native to Stripe — useful for brands running subscription boxes or replenishment models internationally.

Best fit

Strong choice for brands with developer resource and complex payment flows. Stripe's core payment processing incurs per-transaction fees — factor these into your margin calculations at volume.

PayPal

PayPal Business is the trust-signal payment option that a meaningful share of US shoppers — and international buyers — expect to see at checkout. Some shoppers will abandon a cart rather than enter card details on an unfamiliar site, but they'll pay via PayPal without hesitation.

Strengths

• Accepts payments from over 200 global markets supporting 140 currencies — one of the broadest reach profiles of any payment tool in this stack.
• Seller Protection covers eligible transactions against chargebacks, reversals, and fees — meaningful for cross-border sales where dispute rates can be higher.
• Accepts Venmo, PayPal balance, credit/debit, Apple Pay, and Google Pay in a single integration, reducing checkout friction across buyer types.

Best fit

Best used alongside Stripe rather than instead of it — PayPal as the trust-signal option, Stripe as the primary infrastructure. PayPal often holds funds for 72 hours before they're accessible, so plan your cash flow accordingly.

Tax & duty calculation

This is the most consequential layer in a cross-border stack, and the one most brands underinvest in until something goes wrong. Following the 2018 South Dakota v. Wayfair decision, every US state with a sales tax has economic nexus requirements for remote sellers — including foreign sellers with no US physical presence. Once you cross a state's revenue or transaction threshold, you're obligated to collect and remit. Get the tooling right before you scale, not after.

Avalara

Avalara is a tax compliance platform built to handle the kind of multi-jurisdiction complexity that makes US sales tax genuinely difficult — think 13,000+ tax jurisdictions across 50 states, each with their own rates, product taxability rules, and filing calendars.

Strengths

• Sales and use tax calculation handles the real complexity: product-level taxability, jurisdiction stacking (state + county + city + special district), and economic nexus threshold tracking across states.
• Returns preparation and filing automates the ongoing compliance work — not just calculating what you owe, but actually submitting the returns.
• Exemption certificate management is something most brands overlook until they're audited. Avalara handles it systematically.

Best fit

Strong fit for brands hitting economic nexus in multiple US states, or those with complex product catalogues where taxability varies by state. Avalara's functionality is split across multiple products that can be purchased and combined — scope your actual needs before signing up.

Zonos

Zonos is built specifically for the cross-border use case: calculating landed costs, classifying HS codes, remitting taxes in international markets, and presenting a localised checkout experience. Where Avalara handles domestic US tax complexity, Zonos handles the international side.

Strengths

• Duty and tax calculation with guaranteed landed cost — Zonos backs its calculations, meaning if the number shown at checkout is wrong, they cover the difference. That's a meaningful commitment for brands using a Delivered Duty Paid (DDP) strategy.
• Automated HS classification reduces the manual work of categorising products for customs — a genuine time sink at scale.
• Localised checkout in multiple currencies and languages, with fraud protection built in.

Best fit

Essential for any brand shipping physical goods internationally and showing landed cost at checkout. Zonos doesn't handle the physical shipping or package handling — that's ShipBob's job.

Global fulfilment

Consumer expectations in the US are unforgiving: 74% of online shoppers expect delivery within two days. Shipping from a warehouse in Germany or Australia to a US customer and hitting that window isn't realistic. A US-based 3PL solves this by positioning your inventory inside the market before orders are placed.

ShipBob

ShipBob is a global fulfilment network with more than 60 fulfilment centres, including significant US coverage, designed to let e-commerce brands outsource pick-pack-ship operations while maintaining real-time inventory visibility. For a foreign brand entering the US, it's the most practical way to get inventory into the market without leasing warehouse space.

Strengths

• The 2-Day Express Shipping Program lets US customers receive orders within two days from strategically located fulfilment centres — meeting the baseline expectation without building your own US logistics network.
• Real-time inventory management and tracking across all fulfilment locations gives you visibility without manual reconciliation. If you're also tracking inventory across channels, see our guide on syncing Amazon FBA inventory to Google Sheets for a sense of the reporting flows involved.
• Returns management is included — ShipBob handles inbound returns and restocking, which simplifies the cross-border returns loop considerably.

Best fit

Best for brands shipping meaningful volume (not one-off test orders) into the US who want outsourced fulfilment with multichannel integration. ShipBob charges processing fees for returns that aren't included in standard fulfilment pricing — worth modelling if your return rate is above average for your category.

Website localisation

Localisation is more than translation. It's currency display, hreflang tags so your German-language pages don't cannibalize your English SEO, local payment method visibility, and product descriptions that read naturally in the target language. The two tools here serve different scale points — one for fast deployment, one for enterprise-level content operations.

Weglot

Weglot is a no-code localisation tool that installs on your existing site and automatically detects, translates, and serves multilingual content — including language-specific URLs and hreflang tags for SEO. For a brand that needs to go multilingual without a developer project, it's the fastest route.

Strengths

• AI translation with automatic content detection means new product descriptions, blog posts, and landing pages get translated without manual triggers — new content syncs in real time.
• Multilingual SEO is handled properly: language-specific URLs, hreflang tags, and translated metadata rather than just translated page content.
• The visual translation editor lets you review and adjust translations in context, on the live page — which matters when you're checking tone, not just accuracy.

Best fit

Ideal for SMEs needing fast, no-code multilingual deployment. The free tier is limited to 2,000 translated words and one language — fine for testing, but you'll need a paid plan for any real deployment.

Smartling

Smartling is an enterprise-grade Translation Management System (TMS) with automated translation workflows, AI-powered quality checks (including tone and bias detection), and a Global Delivery Network for website localisation at scale.

Strengths

• Automated translation workflows reaching up to 99% automation according to Smartling's own documentation — relevant for brands producing high volumes of product content across multiple languages at once.
• LanguageAI™ includes quality checks that go beyond grammar: tone consistency, bias detection, and brand voice adherence across markets.
• Real-time analytics and reporting on localisation spend and performance give ops teams visibility into which markets are getting content and at what quality.

Best fit

Right tool for enterprise brands running multi-market content operations with translation teams. The 'Free to Start' plan includes translation memory for 180 days — after that, evaluate whether a paid plan makes sense for your volume.

Returns management

Cross-border returns are where a lot of brands quietly lose money and customer trust at the same time. Customers expect international returns to be as seamless as domestic ones — even when the logistics are objectively harder. The goal of a returns tool in this stack is to convert returns into exchanges where possible, and make the unavoidable refunds as low-friction as possible. For more context on the Shopify-specific landscape, see our roundup of the best Shopify returns apps.

Loop Returns

Loop Returns is a post-purchase operations platform originally built for Shopify brands, designed to steer customers toward exchanges instead of refunds through its Shop Now and Instant Exchange features. At high order volumes, shifting even a fraction of returns to exchanges has a material impact on revenue retention.

Strengths

• Exchange-first return flow — Shop Now lets customers browse the full catalogue during a return, not just swap for the same item — which increases the chance of retaining revenue from a return that would otherwise be a pure refund.
• Automated return policies and workflows reduce the manual triage work, and fraud detection flags suspicious return patterns before they process.
• Integrates directly with ShipBob and other major 3PLs, closing the loop between the returns portal and the physical handling of inbound inventory.

Best fit

Best for Shopify brands with meaningful return volume who want to recover revenue from returns rather than just process them. Pricing is based on plan and monthly shipment volume — review the Loop Returns pricing page against your shipment estimates before committing.

The stack at a glance

Frequently asked questions

What software do I need to sell online in the US from another country?

At minimum: an e-commerce platform (Shopify or BigCommerce), a payment processor that handles your target markets (Stripe, PayPal, or both), and a tax calculation tool for US sales tax compliance (Avalara for domestic complexity, Zonos for cross-border duty calculation). If you're shipping physical goods, you'll also need a fulfilment solution — either a US-based 3PL like ShipBob, or your own domestic warehouse. Website localisation is worth adding once you're generating meaningful traffic from non-English markets, not necessarily from day one.

How do I handle US sales tax as a foreign e-commerce seller?

This is the compliance question most foreign brands underestimate. Following the 2018 South Dakota v. Wayfair decision, every US state with a sales tax has economic nexus rules that apply to remote sellers — including those with no US physical presence. Once you exceed a state's revenue or transaction threshold, you're required to register, collect, and remit sales tax in that state. The thresholds vary by state. A tool like Avalara tracks your exposure across states and handles filing. Don't wait until you're audited to sort this out — the penalties compound.

What is the best way to ship e-commerce products to the US?

For brands outside the US, the most practical approach is pre-positioning inventory inside the US via a 3PL like ShipBob. That means shipping a larger consolidated batch to a US fulfilment centre rather than dispatching individual orders internationally for every sale. Once inventory is stateside, customers get domestic shipping speeds and costs. The alternative — shipping each order internationally from your home country — is slower, more expensive per unit, and very difficult to reconcile with the two-day delivery expectation that a large portion of US shoppers hold.

How do I calculate duties and taxes for selling in the US?

Landed cost — the true cost of getting a product to a customer — combines the product value, international freight, customs duties, tariffs, brokerage fees, and applicable taxes. Calculating this manually per SKU per country isn't realistic at any volume. Zonos automates HS classification and duty/tax calculation and can display the guaranteed landed cost at checkout, supporting a Delivered Duty Paid (DDP) model where the customer pays everything upfront and receives no surprise fees on delivery. That matters for conversion: unexpected costs at checkout or delivery are one of the biggest drivers of cart abandonment. For US domestic sales tax specifically, Avalara handles the multi-state complexity that Zonos doesn't cover.

Where to start

Not every layer of this stack is equally urgent. If you're just entering the US market, the non-negotiables are: your platform, payments, and tax compliance. Get those three right before anything else. Fulfilment becomes critical once you're generating enough volume that international shipping timelines are actively hurting conversion — for most brands, that's earlier than they expect. Localisation and returns management are genuinely stage-gated: Weglot makes sense once you have traffic from non-English markets worth converting; Loop Returns makes sense once returns are a meaningful operational cost.

And if you're also selling into EU markets — facing packaging EPR, textile labelling requirements, or battery regulation compliance — that's a different but equally important layer. We cover it in detail in the EU expansion stack, and in category-specific guides like France CITEO reporting for foreign sellers and the sustainable operations stack for fashion brands. Cross-border operations rewards the brands that build the infrastructure before they need it — not the ones scrambling to catch up.

Screenshots are from each tool's public pricing or features page, captured June 2026. We are not affiliated with any third-party tool listed unless explicitly noted.

Last verified: June 2026

Returns aren't waste. Excess inventory isn't dead weight. A product used once isn't at the end of its life. That's the operating premise behind the circular economy — and increasingly, it's what the most profitable e-commerce brands we talk to are actually building around.

But "going circular" means nothing without the right software underneath it. You need tools that handle returns without haemorrhaging margin, platforms that turn those returns into resale revenue, systems that track individual units across rental and warranty cycles, and reporting that holds up against an increasingly demanding EU regulatory environment. None of that happens on a spreadsheet.

This article breaks down the full circular economy tech stack for e-commerce brands — what each layer does, which tools are worth considering, and where to start if you're not ready to deploy all of it at once. It's aimed at operations managers and brand founders running mid-market DTC or multi-channel businesses, probably on Shopify or Amazon, who want a sustainable operation without overcomplicating their stack. For broader context, see our EU expansion operations stack and the 7-figure DTC stack.

Reverse logistics

Reverse logistics software manages what happens after a customer decides they don't want something. Done badly, returns eat your margin and your CS hours. Done well, they convert a refund into an exchange, retain revenue, and feed usable stock back into your resale or refurb channel. This is the first layer most brands build — and the one that pays back fastest.

Loop Returns

Loop Returns is an exchange-first post-purchase platform built primarily for Shopify brands. The core idea is that a return should be a chance to keep the customer spending — not just an outbound refund. The "Shop Now" feature lets customers browse the full catalogue during the return flow and apply their return credit to anything, not just a straight swap of the same item. For a brand processing 500 returns a month, converting even 20% of those into exchanges at a similar AOV adds up quickly.

Strengths

• Exchange-first return flow with Shop Now and Instant Exchanges keeps revenue in-house rather than triggering a refund
• Automated return policies and workflows reduce manual CS handling at volume
• Built-in fraud detection protects against serial returners and policy abuse

Best fit

High-volume Shopify brands that want to convert returns into retained revenue rather than just process refunds cleanly. One thing to model before you commit: order tracking pricing is based on plan and monthly shipment volume, with a flat fee covering a set estimate and a per-shipment fee above that threshold. If you're weighing options, our roundup of Shopify returns apps covers the broader landscape.

AfterShip Returns

AfterShip Returns is a returns automation platform covering branded returns pages, automated resolution workflows, and incentivised exchanges. It integrates with a wider range of platforms than Loop — including BigCommerce and WooCommerce — so if you're not Shopify-native, this is usually the more natural fit.

Strengths

• Branded returns page keeps the post-purchase experience on-brand rather than handing customers off to a generic portal
• Real-time return shipment tracking cuts "where's my refund?" tickets
• Incentivised exchanges and store credits give brands levers to retain revenue during the return flow

Best fit

Multi-platform brands (Shopify, BigCommerce, WooCommerce) or those at earlier volume stages where cost efficiency matters more than enterprise-level exchange automation. Worth knowing: all pricing tiers cap annual return volumes, and overages incur additional per-return fees — so model your projected return volume before choosing a tier.

Recommerce platforms

Returns that can't go back out as new don't have to be written off. Recommerce platforms turn graded, non-new stock into a revenue-generating resale channel — either embedded in your own storefront or routed through a managed marketplace. This is the layer that closes the loop between reverse logistics and actual recovered margin.

Arrive Recommerce

Arrive Recommerce is a full-stack recommerce solution covering SKU itemisation, grading, catalogue integration, and branded resale storefronts. The core idea: your non-new returns, excess inventory, and damaged goods get routed into a resale channel that sits inside your own brand experience — not offloaded to a third-party liquidator at pennies on the pound.

Strengths

• Recommerce Management System covers the full operational workflow: identification, grading, routing, and catalogue integration
• Ecommerce storefront technology embeds branded resale directly into your native website
• Full Stack Analytics combines front-end sales data with back-end operational metrics so you can see actual recovery rates by SKU

Best fit

Brands with enough return or excess stock volume to justify a dedicated resale channel. Requires physical return processing either in-house or through a designated 3PL — factor in that operational overhead before signing up.

Treet

Treet is a branded resale platform with a particular focus on customer retention and marketing automation around the secondhand experience. It connects recommerce with loyalty, post-purchase emails, and AI-driven shopping recommendations — a more complete CX play than pure recommerce operations tools tend to offer.

Strengths

• Automated Marketing Engine (Price Drop Alerts, Post-Purchase Emails, AI Shopping Recs) drives resale conversion without manual campaign work
• Integrates directly with Loop, Happy Returns, and major loyalty platforms including Yotpo and LoyaltyLion
• Launch is measured in days rather than months — a meaningful difference for lean teams

Best fit

Fashion and lifestyle brands that want resale to feel like a proper part of their brand story, not a liquidation outlet. One gotcha worth knowing: products historically deleted from Shopify won't appear in the Treet Product Catalog and need manual upload — so audit your catalogue hygiene before onboarding. Fashion brands should also read our sustainable operations stack for fashion brands for the broader compliance context.

Rental and subscription management

Product-as-a-service is still niche for most e-commerce brands, but it's growing fast in furniture, baby equipment, outdoor gear, and electronics. Managing recurring billing, asset tracking, and return logistics for rented or subscription physical products requires purpose-built tooling. Standard Shopify subscription apps weren't designed for it.

circuly

circuly is a subscription and rental management platform built specifically for physical products. It handles the full lifecycle: recurring billing, asset tracking, refurbishment status, dunning, and customer self-service for swaps, returns, and payment retrial. It integrates with Shopify, WooCommerce, and Shopware, and connects to Stripe and Adyen for payment processing.

Strengths

• Product and asset tracking covers inventory, returns, and refurbishing status — not just billing cycles
• Automated dunning and debt collection handles the awkward payment-failure scenario without manual intervention
• Flexible pricing logic supports complex rental models (short-term, long-term, swap-based)

Best fit

Brands launching a product-as-a-service or circular rental model from scratch. One thing to know: the default shop cart processes rent or buy orders but not both simultaneously. You'll need the circuly cart for combined transactions — a meaningful consideration if your store sells both ways.

Supercycle

Supercycle is a Shopify-native platform covering calendar rental, subscription rental, membership-based item swapping, and serialised resale with full item history. It's the most tightly integrated option for brands that want circular models running directly inside their Shopify storefront and POS without a separate system.

Strengths

• Covers multiple circular models in one platform: calendar rental, subscription, membership swap, and resale with history
• Risk management tools include ID verification, e-signatures, deposits, and card vaulting — essential for high-value rental items
• Native Shopify POS integration means in-store rental and online rental run on the same inventory

Best fit

Shopify merchants who want rental and resale to live natively in their existing storefront. Trade-in functionality is listed as coming soon — if that's a core requirement, factor that into your timing.

Warranty and repair management

This is the circular layer most brands underinvest in. It's where you extend product life rather than just processing an end-of-life return. Done well, it reduces refund rates, generates repair revenue, and feeds data back into product development. Dedicated tools outperform bolted-on helpdesk workflows here by a wide margin.

Claimlane

Claimlane centralises returns, warranty claims, and aftersales requests into a single workflow platform with an AI agent for faster, more consistent decisions. It's built for retailers, suppliers, and manufacturers handling both B2B and B2C claim volumes — so if you're also managing supplier claims (defective goods back up the supply chain), it handles both directions.

Strengths

• AI agent makes warranty and return decisions faster and more consistent, reducing per-claim handling time
• Centralised management of returns, warranty claims, and repair requests eliminates the multi-inbox problem
• Extensive integration list covers Shopify, Salesforce, NetSuite, SAP, Zendesk, Gorgias, and more

Best fit

Brands with meaningful B2B or wholesale relationships alongside their DTC operation, or any brand with complex claim types across multiple product categories. The platform is fully responsive on mobile but doesn't have a dedicated mobile app — not a dealbreaker, but worth knowing for field-based teams.

Dyrect

Dyrect focuses on product registration and warranty claims. Customers register products after purchase, which creates a first-party data asset for the brand while enabling structured warranty claim management — a cleaner alternative to manual proof-of-purchase verification.

Strengths

• Drag-and-drop registration form builder means setup doesn't require developer resource
• Integrates with Klaviyo, ActiveCampaign, and Mailchimp, so registered product data flows directly into CRM and retention campaigns
• Customer self-service portal reduces warranty claim handling load on support teams

Best fit

Consumer electronics, appliances, or any brand where product registration is a natural post-purchase behaviour. Lower pricing tiers include "Powered by DYRECT" branding — upgrade if white-labelling matters to your brand experience.

Sustainability and ESG reporting

This layer sits at the intersection of marketing and compliance. For most DTC brands, the immediate priority is being able to make credible sustainability claims at checkout — not filing a full CSRD report. But as EU regulations tighten (France's CITEO reporting requirements being one example), the reporting layer will matter more operationally, not just for brand positioning.

EcoCart

EcoCart adds green shipping protection and live sustainability impact displays to the Shopify checkout — carbon offset contributions, impact counters, cashback loyalty incentives tied to sustainable choices. It's more checkout-experience tooling than backend ESG reporting, but for DTC brands it's the fastest way to make sustainability tangible at the point of purchase.

Strengths

• Green shipping protection at checkout gives customers a visible, actionable sustainability option without friction
• Live impact counters, pop-ups, and branded landing pages make sustainability claims concrete rather than generic
• Merchant portal provides real-time metrics so you can track actual offset volumes and customer engagement

Best fit

Shopify-native DTC brands that want sustainability built into the checkout experience and loyalty mechanics. Note that EcoCart charges may appear separately from your standard Shopify invoice — check billing setup during onboarding.

Product lifecycle management

PLM sits furthest upstream in the circular stack — it's where product design, materials data, and supplier collaboration live. For e-commerce brands, PLM matters increasingly because of the EU's Digital Product Passport requirements. The DPP is mandatory under the Ecodesign for Sustainable Products Regulation (ESPR) and a key action under the Circular Economy Action Plan. The European Commission expects DPP requirements to cover most physical goods sold in the EU by 2030, with batteries first — mandatory from February 2027.

Propel

Propel is a PR-focused CRM platform with AI pitch writing, press release generation, and media monitoring. It's genuinely useful for communications teams managing sustainability narratives and ESG announcements. But let's be clear: this is a PR tool, not a product data or DPP compliance tool. If you need PLM in the product-traceability sense, Arena PLM below is the relevant option.

Strengths

• AI Tailored Pitch Writer and AI Press Release Writer speed up sustainability communications without an agency
• Media Contact Database and campaign performance analytics keep PR activity measurable
• Unlimited contacts on all tiers means it scales without per-contact pricing friction

Best fit

Brands with an active PR function managing sustainability storytelling, press coverage, and media outreach. Not a product data or compliance tool — don't buy it expecting DPP functionality. The Essentials tier limits monitoring to 10 alerts, which may be tight if you're tracking multiple sustainability topics.

Arena PLM

Arena PLM (now under PTC) is a cloud-native product lifecycle management platform covering bill of materials management, change management, document control, quality, and supplier collaboration. For e-commerce brands selling physical goods into EU markets, this is the layer where DPP-relevant product data — materials composition, supplier information, disassembly instructions — gets captured and managed.

Strengths

• BOM and Change Management keep product specifications accurate across development and into production — critical for DPP data quality
• Supplier Collaboration tools bring supplier data into the same system rather than leaving it in email chains
• Cloud-native with integrations to CAD, ERP, and CRM systems

Best fit

Brands with genuine product development complexity — multiple SKUs, multiple suppliers, regulatory compliance requirements. Pricing is contract-based with a minimum 12-month subscription. This is an enterprise-tier investment, not something you trial casually.

Inventory and compliance management

Running a circular stack means more SKU states to track — new, returned, graded, refurbished, rented, under warranty. Multi-channel inventory management and compliance reporting sit underneath all of the above, holding the operational picture together.

Ceendesis

Ceendesis combines multi-channel inventory management, EPR compliance reporting, and marketplace-to-accounting synchronisation in a single platform — which matters specifically when your circular operations create more data flows to reconcile. If you're running resale and rental alongside new stock, your inventory layer needs to handle multiple product states across multiple channels, not just standard inbound/outbound. Compliance reporting for packaging and batteries (including the 2027 battery DPP requirements) is built in rather than bolted on.

Strengths

• Combines multi-channel inventory, EPR compliance, and marketplace-to-accounting sync in one platform
• Built for brands selling on Shopify, Amazon, eBay, Walmart, and TikTok Shop
• Native Xero and QuickBooks reconciliation for marketplace payouts — relevant if recommerce revenue needs clean accounting separation. See our guides on reconciling Shopify payouts in Xero and connecting Amazon Seller Central to QuickBooks

Best fit

Brands on 2+ marketplaces — overkill for single-channel Shopify-only stores. Visit ceendesis.com for current pricing.

The stack at a glance

Frequently asked questions

What is a circular economy tech stack?

A circular economy tech stack is the set of software tools a brand uses to extend product life beyond the initial sale — covering returns management, resale, rental, repair, warranty, and sustainability reporting. It's a distinct software category from standard e-commerce ops tooling because it tracks products through multiple lifecycles rather than just inbound procurement and outbound fulfilment. The stack typically spans four to six categories depending on the business model.

How can e-commerce brands implement a circular business model?

Start with the highest-impact, lowest-complexity layer: reverse logistics. Getting an exchange-first return flow in place (Loop or AfterShip) is the fastest way to recover margin from returns. From there, add a recommerce channel (Arrive or Treet) to monetise stock that can't be resold as new. Warranty and repair management comes next if your product category has meaningful post-purchase service needs. Rental and subscription models require more operational infrastructure and are best approached once the returns and resale layers are stable. For brands selling into the EU, compliance tooling for EPR and eventually the Digital Product Passport should be planned in parallel — not left until you get a penalty notice. Our PO workflow automation guide covers how to build cleaner upstream processes that support circular operations.

What software is needed for reverse logistics and recommerce?

Reverse logistics software splits into a few functional layers: self-service return portals, automated disposition workflows (refund, exchange, repair, resale), carrier management, and fraud detection. Brands rarely buy one tool to cover all of it. The more common approach is a return management platform (Loop or AfterShip) feeding into a recommerce platform (Arrive or Treet) for non-new stock disposition. AI is increasingly used to make disposition decisions at intake — routing items to the right channel (refund, repair, resell, recycle) without manual assessment at scale. Inventory management sits underneath all of this to track stock states across channels. If you're weighing options across the returns space, our Shopify returns apps comparison goes deeper on the returns layer specifically.

How does the Digital Product Passport (DPP) enable a circular economy?

The DPP is a data record — stored digitally and typically accessed via a QR code or RFID — that captures a product's materials, origin, repairability, disassembly instructions, and end-of-life options. It gives repair technicians, refurbishers, and recyclers the information they need to actually act on a product rather than landfill it. That's what makes it a genuine circular economy enabler rather than just a compliance exercise. The DPP is mandatory under the ESPR and phases in by product category. Battery products face the first hard deadline — February 2027 for industrial and EV batteries above 2 kWh — with most other physical goods expected to be in scope by 2030. For brands selling battery-containing products, this isn't a distant planning exercise. Our EU Battery DPP guide covers what compliance looks like in practice for e-commerce sellers.

Where to start — and what to defer

If you're an early-stage DTC brand doing under £2 million in revenue, the essential tier is simple: a returns management platform and basic inventory tracking. That's it. Everything else is noise until your return volume justifies the tooling overhead.

At the £2–10 million stage, add a recommerce channel. Even routing 15–20% of returns into a graded resale stream materially changes your unit economics on returned goods. A warranty and product registration tool also starts paying back at this stage — both in reduced refund rates and in first-party customer data.

Rental, subscription, and full PLM are mid-to-large brand territory. They need genuine operational capacity to run well. Arena PLM in particular is a significant procurement decision — don't evaluate it until DPP compliance is an active regulatory priority for your product category.

And throughout all of it, make sure your inventory layer can actually track what's happening. Multi-channel brands running resale alongside new stock need an IMS that handles multiple SKU states — not a spreadsheet with a returns tab bolted on. For a broader look at building operations infrastructure that scales, see the full EU expansion stack and our shipping software guide for the outbound logistics side of the picture.

Screenshots are from each tool's public pricing or features page, captured June 2026. We are not affiliated with any third-party tool listed unless explicitly noted.

Last verified: June 2026

Amazon's Buyer-Seller Messaging system works. It is not, however, a pleasant place to spend your day — especially when you're also handling Shopify support, returns emails, and the occasional warehouse fire drill. Every channel in a separate tab is a slow way to run customer service. And on Amazon specifically, slowness has real consequences: miss the 24-hour response window and your seller account health takes a hit.

Gorgias is already the helpdesk of choice for a lot of Shopify-first brands, so the natural question is: can you pull Amazon messages into it too? Yes — you can, but not with a simple one-click native connection. Amazon doesn't play nicely with direct helpdesk integrations, which means you need a middleware connector sitting between your Seller Central account and Gorgias. This guide walks you through every method, honest about the tradeoffs.

If you're building out a broader operations stack — combining support tooling with accounting, inventory, and marketplace expansion infrastructure — getting your support layer sorted first is the right call. Everything downstream runs better when your team isn't drowning in message queues.

Before you start

• Active Amazon Seller Central account
• Gorgias account (any paid tier that supports integrations)
• Subscription to a third-party connector tool (e.g., ChannelReply, Commercium)
• Admin access to both your Gorgias workspace and your Amazon Seller Central account
• Your Amazon Seller Central store region noted (US, EU, UK) — some connector tools require you to connect each region separately

Methods at a glance

Method 1: connector tool (ChannelReply or Commercium)

This is the right route for the vast majority of sellers. ChannelReply and Commercium act as middleware — they pull your Amazon Buyer-Seller messages, attach order metadata, and push everything into Gorgias as structured tickets. The connector also handles reply routing back to Amazon, so your agents never need to leave Gorgias. Both require a paid subscription; neither offers a meaningful free tier for production use.

1. Sign up for your chosen connector tool (ChannelReply or Commercium) and complete their onboarding flow. You'll be asked to select Gorgias as your helpdesk during setup.
2. Authorise the connector to access your Gorgias account — click the OAuth prompt when it appears, log in to Gorgias if needed, and grant the requested permissions. You'll be redirected back to the connector dashboard with a "Gorgias connected" confirmation.
3. Connect your Amazon Seller Central account inside the connector dashboard. This typically means clicking "Add marketplace" → "Amazon", then authorising via Amazon's SP-API flow. If you sell across multiple regions (e.g., Amazon US and Amazon UK), add each region as a separate connection.
4. Configure your message routing rules in the connector — set which Amazon message types should create tickets in Gorgias (buyer messages, order notifications, A-to-z claim alerts). A test ticket should appear in your Gorgias inbox within a few minutes.
5. Verify that order data is appearing in the ticket sidebar in Gorgias. Open the test ticket and check the right-hand sidebar — you should see the buyer's order ID, item purchased, order status, and tracking information pulled through automatically.
6. Send a test reply from Gorgias and confirm it lands in Seller Central's Buyer-Seller Messaging thread. Log into Seller Central in a separate tab and check the thread manually. Do this before it affects a real customer.

For the exact steps Gorgias documents on their end, refer to the official Gorgias integration guide.

Method 2: native app (Gorgias App Store)

Gorgias maintains an App Store where vetted integration partners publish connectors. Some connector tools — including ChannelReply — publish a listed app here, which means you can initiate the connection from inside Gorgias rather than starting on the connector tool's own website. The underlying technology is identical; you're just starting the flow from a different place. This suits teams who prefer to manage all their integrations from one dashboard.

1. Log in to your Gorgias admin panel and navigate to Settings → App Store.
2. Search for "Amazon" in the App Store search bar. You'll see available marketplace connectors listed — look for ChannelReply or any listed Amazon integration partner.
3. Click "Install" on the connector you want. A permissions prompt will appear outlining what data the app will access in your Gorgias workspace.
4. Accept the permissions and complete the OAuth handshake. You'll be redirected to the connector tool's setup flow.
5. Follow steps 3–6 from Method 1 to connect your Amazon Seller Central account, configure message routing, and verify the integration end-to-end.

And that's genuinely all that's different. The App Store method is really just an alternative entry point into the same connector-tool setup. Don't overthink it.

Method 3: direct API

Amazon exposes a Selling Partner API (SP-API) that includes Messaging endpoints, and Gorgias has its own REST API. In theory, you could build a custom integration that pulls messages from Amazon's SP-API and creates tickets in Gorgias programmatically. In practice, this is a serious engineering undertaking — Amazon's SP-API access requires going through an application approval process, and you'd be responsible for handling rate limits, message threading, reply routing, and failure states yourself. When Amazon changes their API (and they do), your integration breaks. Maintenance burden is high.

1. Apply for SP-API access via the Amazon Developer Console. Complete the use case questionnaire and wait for Amazon's approval — this can take several business days.
2. Register your application and generate your SP-API credentials (Client ID, Client Secret, Refresh Token). Store these securely; you'll need them in your integration code.
3. Build a polling or webhook-based listener that calls Amazon's getMessages endpoint on a schedule to retrieve new buyer messages.
4. Transform the Amazon message payload into a Gorgias-compatible format — map buyer email (or Amazon's anonymised address), order ID, and message body to the appropriate Gorgias ticket fields.
5. POST the transformed payload to the Gorgias API (POST /api/tickets) to create a new ticket. Include the order data as custom fields or sidebar metadata.
6. Build a reply listener in Gorgias (via webhooks on ticket updates) that captures agent replies and POSTs them back to Amazon's sendMessage endpoint.
7. Test end-to-end with a real Amazon buyer message and confirm both directions work — message in, reply out.

Unless you have a developer who knows both APIs well and can maintain the integration over time, use Method 1. The connector tools have already solved these problems and handle API version changes for you.

Common errors and how to fix them

Replies sent from Gorgias don't appear in Amazon Seller Central

This is the most common complaint, and it usually comes down to reply routing misconfiguration in the connector tool. Open your connector dashboard, find the reply routing settings, and confirm the outbound path is mapped correctly to your Amazon account. Send a test reply, then check Seller Central directly. If it still doesn't appear, raise a ticket with your connector tool's support team — not Gorgias support, since this is a partner integration. Also check that the buyer's Amazon anonymised email address is being used as the reply-to, not a real email address.

Initial messages don't show full customer or order information

When a brand-new buyer message arrives, some connector tools need a moment to resolve the order data against Amazon's API before populating the ticket sidebar. If you open a ticket immediately and the sidebar looks empty, wait 30–60 seconds and refresh. If order data never appears, check whether your Amazon SP-API connection is still authorised — tokens can expire, and a re-authorisation in the connector dashboard usually fixes it immediately.

Only buyer messages appear — not your own previous replies

This is an Amazon API limitation, not a bug in your setup. Amazon's messaging API surfaces buyer messages to third-party tools, but seller replies sent directly from Seller Central before you set up the integration won't be backfilled. Going forward, once the integration is live, replies sent through Gorgias will appear in both places. For historical threads, check Seller Central directly.

The integration requires a paid third-party subscription

Not an error — but a surprise for sellers who expected a free native connection. There's no way around this currently. Amazon doesn't expose a direct helpdesk webhook that Gorgias can consume without middleware. Budget for a connector tool subscription as a line item in your support stack costs. Given the alternative is a dedicated person manually checking Seller Central all day, the maths almost always work out.

Best practices for managing Amazon support in Gorgias

Once the integration is running, a few habits will make a real difference to how efficiently your team handles Amazon tickets.

Tag Amazon tickets immediately. Set up a Gorgias rule that auto-applies a tag (e.g., amazon, amazon-us, amazon-uk) to every ticket that comes in through the connector. This keeps filtering and reporting clean from day one, and means macros can be scoped to fire only on Amazon tickets.

Build macros for your top five Amazon message types. For most sellers, those are: order status enquiry, where's my refund, item not received, wrong item sent, and A-to-z claim notification. A well-built macro pre-fills the order ID and tracking number from sidebar variables — your agent clicks once and the response is 90% done. Every bit of order data the connector pulls into Gorgias can be used as a placeholder in macros.

Watch the 24-hour clock. Amazon's response time requirement is real and it affects your account health. Set up a Gorgias rule that escalates or reassigns any Amazon ticket that's been open for 18 hours without a reply — that gives you a 6-hour buffer before the deadline hits.

Don't try to resolve A-to-z claims from Gorgias. Connector tools like ChannelReply can deliver A-to-z claim notifications to your Gorgias inbox and include a direct link back to Seller Central, but the resolution process itself has to happen in Seller Central. Treat those tickets as alerts, not resolvable support issues.

Automating Amazon support with Gorgias rules and macros

The real leverage from this integration is automation. Once Amazon messages are in Gorgias as structured tickets, the full rules engine applies — the same tools you'd use for Shopify support. A few practical examples.

Auto-respond to order status enquiries. Build a rule that fires when a ticket contains the words "where is my order" or "tracking" and the tag amazon is present. The rule sends a macro that pulls in the tracking number and carrier from the sidebar, then closes the ticket if no reply comes back within 48 hours. For a seller handling 200 orders a day, this deflects a significant chunk of first-contact messages without any agent involvement.

Prioritise feedback and review requests. Amazon sends notifications when a buyer leaves negative feedback. Tag these with amazon-feedback and assign them immediately to your most experienced agent — the faster you respond, the better your chance of resolution before it compounds.

Use Gorgias statistics to track your Amazon response time. Filter your Gorgias reports by the amazon tag and monitor first response time as a standalone metric. If it creeps above 10 hours on average, you've got a staffing or process problem to fix before Amazon notices.

For a broader look at how support tooling fits into your overall operations setup, the 7-figure DTC operations stack breakdown is worth reading alongside this guide.

Frequently asked questions

Can Gorgias integrate with Amazon?

Yes — but it requires a third-party connector tool such as ChannelReply or Commercium. There's no native, direct connection between the two platforms. Once a connector is in place, Amazon Buyer-Seller messages flow into Gorgias as tickets with order data attached.

How do I manage Amazon messages in Gorgias?

Connect your Amazon Seller Central account to Gorgias via a middleware connector tool (see Method 1 above). After setup, all incoming buyer messages appear as tickets in your Gorgias inbox, and replies you send from Gorgias are routed back to the buyer through Amazon's messaging system. Use tags and views to keep Amazon tickets separated from your other channels.

What are the benefits of connecting Amazon to a helpdesk like Gorgias?

Centralisation and speed, mainly. Instead of monitoring Seller Central separately, your team handles Amazon messages alongside every other support channel in one place. Order context — status, tracking, customer history — appears in the ticket sidebar, so agents don't need to look anything up. And because Amazon's 24-hour response requirement isn't negotiable, having Amazon tickets in a managed helpdesk queue with automation and escalation rules makes it much easier to stay on the right side of it.

How can I automate customer service for my Amazon store?

Once Amazon messages are flowing into Gorgias via a connector tool, you can use Gorgias's built-in rules engine and macros to automate responses. Set up rules to auto-reply to common enquiry types (order status, tracking), auto-tag tickets by issue, and escalate anything approaching Amazon's 24-hour deadline. Macros can use Amazon order data as dynamic placeholders, so a single click sends a fully personalised response without any manual data lookup.

Which method should you pick?

For almost every seller reading this: Method 1 or Method 2. They're effectively the same thing with different starting points. The connector tool handles the hard stuff — SP-API authorisation, message threading, reply routing — and you're up and running in under an hour.

Method 3, the direct API build, only makes sense if you have a development team, a compelling reason the connector tools can't satisfy, and the appetite to maintain custom integration code indefinitely. That's a narrow use case.

Get the connector running, build your macros, and spend the time you save somewhere that actually grows the business. If you're expanding into additional marketplaces at the same time, the right listing and operations tooling pairs well with a properly set up support stack.

Last verified: June 2026

If you're selling on FBA and tracking inventory in a spreadsheet by hand, you're running on lag. You download a report, paste it in, do your analysis — and by then the numbers have already moved. For a brand doing 50 orders a day, that's an inconvenience. For one doing 500, it's genuinely expensive. Stockouts cost you the sale and the ranking. Overstock costs you monthly storage fees. Neither is recoverable.

Google Sheets remains the default operations tool for most SME e-commerce brands, and there's nothing wrong with that. It's flexible, shareable, and free. The problem isn't the destination — it's the pipeline. Getting fresh FBA inventory data into Sheets automatically, on a schedule, without someone manually running a report at 8am every morning, is what this guide covers.

We'll walk through four methods: the manual export (which you should understand even if you plan to automate), connector tools, Google Apps Script talking directly to the SP-API, and a brief note on purpose-built integrations. If you've already wired up other Amazon data flows — the process for connecting Seller Central to Google Sheets generally is a useful companion read — some of this will feel familiar.

Before you start

• Active Amazon Seller Central account with FBA inventory (Professional selling plan required for SP-API access)
• Google Account with Google Drive access
• Subscription to a third-party connector tool (if using the connector method)
• Google Cloud Platform project with the Sheets API enabled (if using the direct API or Apps Script method)
• SP-API developer registration approved in Seller Central (for the Apps Script / direct API method) — see Amazon's FBA Inventory API reference for scope requirements

Methods at a glance

Method 1: Manual CSV export from Seller Central

This is the baseline. No setup, no credentials, no third-party tools. Also no automation — a human has to do it every single time, which is exactly why most brands outgrow it quickly. That said, it's worth understanding the export even if you plan to automate, because the field names in the CSV are the same ones you'll reference in any downstream formula or script.

1. Open Seller Central and navigate to Reports > Inventory Reports using the top navigation bar.
2. Select "FBA Manage Inventory" (or "All Listings Report" for a broader view) from the report type dropdown.
3. Click "Request Report" and wait — generation typically takes under a minute for catalogues under a few thousand SKUs.
4. Click "Download" once the status shows Ready. Amazon serves a tab-delimited TXT file.
5. Open a new Google Sheet and go to File > Import. Choose the downloaded file and set the separator type to Tab. Leaving it on Auto-detect or Comma is the most common cause of garbled single-column data.
6. Verify key columns are present: asin, fnsku, available, inbound-quantity, reserved-quantity. These map directly to the fields exposed by the SP-API, which matters if you later automate this.
7. Save the sheet and note the timestamp — this data is already stale the moment it lands.

The honest limitation: manual export is fine for a monthly audit or a one-time reconciliation. It's not a workflow. A brand selling 200 units a day cannot run operations on a spreadsheet that was accurate yesterday morning.

Method 2: Connector tool (Hopted, Zapier, or similar)

Connector tools sit between Amazon and Google Sheets, handle the OAuth authentication for you, and let you schedule automatic pulls without writing a line of code. Hopted is purpose-built for Amazon-to-Sheets syncing and can pull the FBA Inventory report on a schedule. Zapier is more general-purpose but covers the same use case via its Amazon Seller Central integration.

The tradeoff is cost — both require a paid tier for automated, recurring syncs — and some vendor dependency. If the connector goes down or changes its pricing, your pipeline breaks. For most non-technical teams, that's still a better bet than maintaining a custom script.

1. Create an account on your chosen connector tool and select the Amazon Seller Central integration from the app directory.
2. Authenticate your Amazon account by following the OAuth flow — you'll be redirected to Seller Central to grant permissions. Use the same account that owns the FBA inventory you want to sync.
3. Select "FBA Inventory Report" (or equivalent) as the data source. In Hopted this is listed explicitly; in Zapier you'll trigger on a schedule and use the "Get Inventory" action.
4. Connect your Google account and select or create a destination spreadsheet. Specify the target sheet tab and the starting cell — typically A1 on a dedicated "FBA Inventory" tab.
5. Configure the sync schedule. For most mid-volume brands, every hour is sufficient. High-velocity sellers running flash sales may want 15-minute pulls, but check whether your connector plan supports that frequency.
6. Run a manual test sync and verify the data lands correctly. Cross-check three or four SKUs against what you see in Seller Central's Manage FBA Inventory screen.
7. Enable the automation and set up a Slack or email alert for sync failures — connector tools can silently fail if the Amazon token expires or your Seller Central permissions change.

Method 3: Google Apps Script and the SP-API

This is the most technically involved method, but also the most transparent and cheapest to run long-term. You write a script inside Google Apps Script (which lives in your Google Sheet), it authenticates against the SP-API FBA Inventory endpoint, pulls available/inbound/reserved quantities, and writes them to your sheet. You then set a time-driven trigger to run it on whatever schedule you want.

One important reality check: Amazon's SP-API doesn't push data — it only responds to requests. So "live" inventory in this context means "pulled every N minutes." For most brands, every 30–60 minutes is live enough.

1. Register as a developer in Seller Central under Apps & Services > Develop Apps. Complete the use case description — for internal inventory tracking, select "Private Seller App." Amazon will review this, which can take a few days.
2. Create an IAM user in AWS with the AmazonSPAPIRolePolicy attached. Note the Access Key ID and Secret Access Key — you'll need these in your script.
3. Generate an LWA (Login with Amazon) client ID and secret from your developer application in Seller Central. These are separate from your AWS credentials and handle the OAuth token exchange.
4. Open your Google Sheet, go to Extensions > Apps Script, and create a new script file.
5. Store your credentials using Apps Script's PropertiesService rather than hardcoding them: PropertiesService.getScriptProperties().setProperty('LWA_CLIENT_ID', 'your-id'). Do the same for the client secret, refresh token, AWS keys, and marketplace ID.
6. Write the token exchange function. Make a POST request to https://api.amazon.com/auth/o2/token with your LWA credentials and refresh token to get a short-lived access token. The SP-API uses AWS Signature Version 4 for request signing — open-source Apps Script implementations of this exist on GitHub and save significant time.
7. Call the FBA Inventory API endpoint: GET https://sellingpartnerapi-na.amazon.com/fba/inventory/v1/summaries (adjust the regional domain for EU: sellingpartnerapi-eu.amazon.com). Pass granularityType=Marketplace, granularityId (your marketplace ID), and details=true to get the full breakdown including fulfillableQuantity, inboundWorkingQuantity, and reservedQuantity.
8. Parse the JSON response and write the results to your sheet. A simple loop over inventorySummaries writing ASIN, FNSKU, condition, and the quantity fields to sequential rows is sufficient for most use cases.
9. Set a time-driven trigger under Triggers in the Apps Script editor. Choose "Time-driven," set to every 30 or 60 minutes depending on your sales velocity.
10. Add error logging — write failed runs to a separate "Errors" tab with a timestamp, so you know when the token has expired or the API has returned a throttling error (HTTP 429).

Method 4: Direct API integration (custom application)

If you're building a proper internal ops tool — or pulling FBA inventory data into a wider system alongside, say, a Dynamics 365 ERP or a custom dashboard — a direct API integration built outside Google's ecosystem may be the right call. The SP-API is the same; the difference is that your application lives on your own infrastructure and writes to Sheets via the Google Sheets API.

1. Enable the Google Sheets API in your Google Cloud Platform project under APIs & Services > Library.
2. Create a service account in GCP and download the JSON key file. Share your target Google Sheet with the service account's email address (with Editor access).
3. Build your SP-API authentication layer using your preferred language — Amazon's SP-API has official SDK support for Python, Java, and C#. Handle LWA token exchange and AWS SigV4 signing as in Method 3, but in your application's language.
4. Call the FBA Inventory API on your chosen schedule using a cron job or a managed scheduler (AWS EventBridge, Google Cloud Scheduler, etc.).
5. Write the inventory data to Sheets using the Google Sheets API's spreadsheets.values.update or batchUpdate method. The Sheets API reference covers authentication, range notation, and value input options in detail.
6. Handle pagination — the FBA Inventory API returns results in pages using a nextToken parameter. If your catalogue has more than a few hundred active ASINs, you'll need to loop through all pages before writing to the sheet.

This is the approach to consider if you're thinking about a full seven-figure operations stack or planning to add purchase order automation downstream — see our guide on automating your e-commerce PO workflow for what that looks like in practice.

Common errors and how to fix them

Google Sheets displays garbled single-column data after import

Amazon's inventory reports download as tab-delimited TXT files, not standard CSVs. When you import via File > Import, you have to set the separator to Tab manually. Leave it on Auto-detect or Comma and the entire row lands in column A. Re-import with the correct delimiter. For very large catalogues (tens of thousands of SKUs), also check that the sheet hasn't hit Google Sheets' row limit — consider splitting by fulfilment centre or product category if needed.

SP-API returns HTTP 401 Unauthorized

LWA access tokens expire after one hour. If your Apps Script trigger runs on a longer interval, or your token exchange function isn't being called before each API request, you'll hit 401s. The fix: always call the token exchange function at the start of your main function. Never cache the access token across script executions.

SP-API returns HTTP 429 Too Many Requests

The FBA Inventory API has rate limits — check the SP-API FBA Inventory reference for the current burst and restore rates for each endpoint. If you're hitting 429s, add exponential backoff with jitter to your retry logic, and avoid running multiple triggers simultaneously.

Connector tool syncs stop silently

OAuth tokens for Amazon Seller Central can expire or be revoked — particularly if you change your Seller Central password or revoke app permissions. Most connector tools won't alert you when this happens. Set up a simple monitoring formula in your sheet that flags when the "last updated" timestamp hasn't changed within your expected sync window. Something like =IF(NOW()-B1>2/24,"SYNC STALE","OK") in a header cell will catch failures visually.

Scraping Seller Central directly doesn't work

Amazon aggressively blocks automated browser access with CAPTCHAs and IP-based rate limiting. Don't attempt it. The SP-API exists specifically to give programmatic access to this data — use it. Any scraping approach is unreliable and against Amazon's terms of service.

Frequently asked questions

How do I automatically export Amazon inventory reports?

You can't fully automate the manual download from Seller Central — it requires human interaction. For true automation, use a connector tool or the SP-API to pull inventory data on a schedule. Both Hopted and Zapier support scheduled Amazon-to-Sheets syncs without manual intervention.

How do I get FBA data into Google Sheets?

There are four routes: manual CSV download and import, a connector tool with a paid subscription, Google Apps Script calling the SP-API directly, or a custom application using both the SP-API and the Google Sheets API. For most teams without developer resource, a connector tool is the fastest path. For full control and no recurring tool cost, Apps Script is the right call.

Can I link Amazon Seller Central to a spreadsheet?

Yes, but not natively — Amazon doesn't offer a direct Sheets integration out of the box. You link them either through a third-party connector tool or by building an SP-API integration yourself. The result is a scheduled pull of your inventory data rather than a true real-time feed, because the SP-API is request-based, not push-based.

What is the best way to track FBA inventory?

For small catalogues and infrequent audits, a manual CSV export into Sheets is fine. For ongoing operations, an automated sync via connector tool or Apps Script is far more reliable — it removes the human step that causes data to go stale. If you're scaling to multiple channels, a dedicated inventory management system will serve you better than any spreadsheet-based approach over the long term. For broader context on where inventory tracking fits in a growing stack, see our guide to building an e-commerce operations stack for EU expansion.

If you're also syncing Shopify data alongside your FBA inventory, the same principles apply — our guide on syncing Shopify orders to Google Sheets covers the equivalent setup on that side. And if your goal is full Amazon-to-accounting reconciliation rather than just inventory visibility, the Seller Central to QuickBooks guide and our piece on reconciling Shopify payouts in Xero are worth reading alongside this one.

Which method should you pick? If you need something working by end of day and don't want to write code, start with a connector tool — setup is under an hour and the maintenance burden is low. If you're comfortable in Apps Script and want to avoid a recurring subscription, Method 3 is more robust long-term. If you're already running a custom ops platform, or plan to — particularly if you're thinking about channel expansion and tools like syncing Shopify inventory back to FBA — Method 4 gives you the cleanest architecture. The manual export is only defensible for one-off audits. Don't build a business process around it.

Last verified: June 2026

If you sell e-bikes, power tools, or consumer electronics into the EU, there's a deadline coming that most operations teams aren't ready for. The EU Battery Digital Product Passport isn't a labelling tweak or a checkbox — it's a fundamental shift in how product data must be structured, stored, and transmitted from manufacturer to end consumer. And for e-commerce brands, the knock-on effects hit your inventory system, your supplier relationships, and your product listings all at once.

What the EU Battery Digital Product Passport actually is

The EU Battery Digital Product Passport is a structured, machine-readable record attached to every regulated battery. It makes the full lifecycle of that battery transparent to regulators, recyclers, and consumers. It operates under EU Battery Regulation 2023/1542, which replaces the older Batteries Directive and introduces some of the most demanding product data requirements the EU has ever published.

The core idea is straightforward. Every regulated battery must carry a unique identifier — expressed as a QR code on the physical product — linking to a data record hosted in a system accessible to the relevant parties. That record tells the whole story: what's in the battery, how much carbon was emitted making it, what percentage of its materials came from recycled sources, and how it should be handled at end of life.

But here's the thing: the DPP isn't a document you produce once. It's a living record. As a battery moves through the supply chain — from manufacturer to distributor to e-commerce retailer to consumer — the data attached to its DPP can be updated. Repair records. State of health data. Chain of custody. This is genuinely new territory for most SME brands.

Think of it as a passport in the truest sense — a document that travels with the product through its entire life, not just to the point of sale. For a broader look at what these obligations mean when you're scaling into EU markets, our guide to EU expansion operations is worth reading alongside this article.

Who does this affect — and when

The DPP requirements apply to any economic operator — manufacturer, importer, or authorised representative — placing regulated batteries on the EU market. For e-commerce, that typically means you, the brand, even if you're based in the UK or the US.

The regulation covers four main battery categories, and the DPP rollout is phased by category:

If your brand sells e-bikes or light electric vehicles into the EU, 2026 isn't theoretical — it's here. LMT battery DPP requirements begin phasing in during 2026 under the delegated acts the European Commission is finalising. Portable battery requirements (laptop batteries, power bank batteries, tool batteries) follow later, but you need to be building the infrastructure now, not when the deadline lands on you.

One thing many sellers miss: the obligation attaches to the battery, not the finished product. If your electronic product contains a regulated battery and you're placing it on the EU market — whether directly via your Shopify store, via Amazon.de, or through a wholesale distributor — you're in scope. A UK-based brand selling into Germany via an EU-established fulfilment partner still needs a compliant DPP. Multi-country EPR compliance is already complex for packaging; battery DPPs add another layer on top.

What data your DPP actually needs

The data requirements are extensive — and that's putting it mildly. The regulation specifies multiple data categories, and not all of them are public-facing. Some are accessible only to regulators and notified bodies; others are visible to consumers. Getting the access tiers right matters as much as having the data in the first place.

Core data fields required for an LMT or industrial battery DPP include:

• Battery identification: Unique identifier, batch number, manufacturing date, country of manufacture, manufacturer details
• Chemical composition: Cathode, anode, and electrolyte materials — by percentage weight
• Carbon footprint: Total lifecycle carbon footprint in kg CO₂e per kWh, broken down by life cycle stage (extraction, manufacturing, transport, end of life)
• Recycled content: Percentage of cobalt, lithium, nickel, and lead recovered from waste sources (with targets phased in over time)
• Performance and durability: Rated capacity, expected lifetime (cycle count and calendar), capacity fade thresholds
• State of health (SoH): For batteries placed on the aftermarket or reused — current SoH data
• Due diligence: Supply chain due diligence policy covering raw material sourcing (cobalt, lithium, nickel, natural graphite)
• End-of-life: Disassembly instructions, take-back scheme information, hazardous substance labelling

The carbon footprint requirement alone is significant. For an e-bike battery, you'll need lifecycle carbon data from your battery manufacturer — broken out by stage. Many tier-2 and tier-3 Chinese manufacturers don't have this data ready. That supply chain conversation needs to happen now, before the deadline, not after your first shipment is held at customs. The compliance burden here genuinely sits upstream.

And the due diligence piece isn't a tickbox. It requires a documented supply chain policy specifically addressing conflict mineral sourcing for cobalt, lithium, nickel, and natural graphite — the same materials driving the EV battery economy and a growing focus for EU enforcement. If you've already built out responsible sourcing documentation for other regulations (some fashion brands selling into France have done this under AGEC and textile compliance obligations), you'll have a head start.

How to actually build this, end to end

The operational question is: how do you build this across a product catalogue that might span dozens of SKUs with different battery types?

Start with your supplier data collection process. Every battery you source needs to arrive with a data sheet covering, at minimum, chemical composition, capacity, carbon footprint, and recycled content. Build this into your purchase order terms — require it as a delivery condition. If your supplier can't provide it, that's a supply chain risk you need to resolve before the regulation kicks in. We covered structured PO workflows in our guide to automating purchase order processes, and the same discipline applies here — except now the data payloads are compliance-critical, not just operational.

Once you have the data, you need to host it somewhere. The DPP requires that the QR code on the physical battery links to a record accessible via a public URL (for the consumer-facing tier) and, separately, to a secure record accessible to regulators and authorised bodies. The European Commission is still finalising the exact technical architecture for the EU-wide DPP registry, but brands should be building their own data infrastructure now regardless — the QR code must resolve to something when scanned.

In practice, here's the workflow most brands are moving toward:

1. Data ingestion: Collect battery data from manufacturers at the SKU level — ideally structured (JSON or XML) rather than unstructured PDFs.
2. Unique identifier generation: Generate a globally unique battery ID per unit or batch (depending on category requirements), aligned with the GS1 Digital Link standard where applicable.
3. QR code production: Commission QR codes that encode the identifier and link to the hosted DPP record. These must be physically affixed to or printed on the battery.
4. Inventory tagging: Link each physical unit (or batch) to its DPP record in your inventory management system so you can track which DPP applies to which stock.
5. Ongoing updates: For batteries re-entering the market (repaired, refurbished), update the SoH data in the DPP record.

The inventory piece is easy to overlook. If you're selling across multiple channels — your own Shopify store, Amazon EU marketplaces, wholesale — you need the DPP identifier tied to the SKU at the inventory level so that the right DPP data travels with every unit dispatched. Syncing inventory across Shopify and Amazon with that level of product-level data attached requires proper systems, not spreadsheets.

The technology question — and why most brands get it backwards

Most brands overthink the technology and underthink the data. Generating a QR code takes seconds. The hard part is having clean, complete, structured data to put behind it, and a system that keeps that data accurate as products move through your supply chain and fulfilment operations.

Ceendesis Battery Compliance is built specifically for e-commerce brands facing this problem. It centralises your battery product data by SKU, generates unique DPP identifiers, hosts the required data tiers (public consumer-facing, restricted regulator-facing), and integrates with your inventory operations so that stock movements don't break the chain of DPP traceability. It's designed for operations managers at SME brands — not enterprise compliance teams with dedicated legal departments.

The broader technology stack matters too. If you're running multi-channel operations across wholesale and marketplace channels, your inventory platform needs to carry product-level compliance attributes alongside the usual stock data. That's a data architecture decision — and it's far easier to make at the start of a compliance project than to bolt on after the fact.

For brands already using Ceendesis IMS, the integration between IMS and our compliance tools means DPP identifiers can be linked directly to your product catalogue, so fulfilment and compliance data live in the same place. No double-entry. No "which spreadsheet has the battery data?" conversations at 11pm before a major restock arrives.

When we were running our own e-commerce brands before building Ceendesis, the thing that killed compliance projects wasn't complexity — it was data scattered across supplier emails, product spec sheets in Dropbox, and half-updated spreadsheets. A structured system isn't a luxury; it's the only way this works at scale.

Why getting ahead of this actually pays off

Early DPP adoption gives e-commerce brands a real commercial edge — particularly in B2B and wholesale channels where buyers are increasingly screening suppliers on sustainability documentation. Clean, auditable battery lifecycle data isn't just a regulatory requirement; it's a procurement differentiator.

Consider the carbon footprint data requirement. Brands that build robust carbon tracking into their battery sourcing process now will be able to make genuine, verifiable green claims — the kind that survive scrutiny under the EU Green Claims Directive, which is tightening. Vague sustainability marketing is getting harder to defend. Specific lifecycle data, attached to a battery DPP, is the opposite of vague. If you're already thinking about this for your fashion products, our piece on sustainable operations for fashion brands covers the parallel challenge in textiles.

There's also the refurbishment angle. Brands that maintain accurate DPP records — including state-of-health data — are better placed to participate in battery second-life markets, which are growing fast as EU policy pushes reuse over disposal. A battery with a complete DPP history is worth more in the secondary market than one without. That's not a compliance observation — it's an economic one.

And the operational discipline required to implement DPP compliance — clean SKU-level product data, structured supplier data flows, audit-ready records — is the same discipline that makes your operations more efficient at every level. Compliance projects that improve your data infrastructure pay dividends well beyond the specific regulation that triggered them.

Frequently Asked Questions

What is the primary purpose of the EU Battery Digital Product Passport?

The EU Battery Digital Product Passport makes the full lifecycle of a regulated battery transparent — to consumers, regulators, recyclers, and supply chain actors. It does this by attaching a unique, machine-readable data record to every regulated battery, covering composition, carbon footprint, recycled content, performance, and end-of-life handling. The goal is to support a circular economy for batteries by ensuring accurate, accessible data follows the battery throughout its life.

Which types of batteries require a Digital Product Passport in the EU by 2026?

Light means of transport (LMT) batteries — such as those used in e-bikes and e-scooters with a capacity of 2 Wh or more — are the first category subject to DPP requirements, with phased implementation beginning in 2026 under EU Battery Regulation 2023/1542. Industrial batteries follow on a similar timeline, with EV and portable battery DPP requirements phasing in from 2027 onward.

What specific data points must e-commerce brands provide for the Battery DPP?

Required data includes the battery's unique identifier, chemical composition (cathode, anode, electrolyte by weight), total lifecycle carbon footprint in kg CO₂e per kWh, percentage of recycled content for cobalt, lithium, nickel, and lead, rated capacity, expected lifetime, supply chain due diligence documentation, and end-of-life instructions. Some data fields are publicly accessible via the QR code; others are restricted to regulators and notified bodies. The exact field requirements vary by battery category and are specified in delegated acts under the regulation.

How do online sellers implement QR codes to link to the Battery Digital Product Passport?

The manufacturer or importer placing the battery on the EU market must generate a unique battery identifier aligned with recognised standards (such as GS1 Digital Link), host the DPP data record at a resolvable URL, and encode that URL into a QR code physically affixed to the battery. The QR code must meet minimum size and durability standards so it remains scannable throughout the battery's life. For e-commerce brands, this means coordinating with manufacturers on label production and ensuring your hosted DPP data stays live and accurate.

What are the potential penalties for non-compliance with the EU Battery Regulation's DPP requirements?

Penalties are set at member state level, so enforcement and fine structures vary by country — but the regulation requires member states to put "effective, proportionate, and dissuasive" penalties in place. Beyond fines, non-compliant batteries can be blocked from sale or ordered withdrawn from the market by national market surveillance authorities. For e-commerce brands, the practical risk is also reputational: major marketplace operators are expected to enforce DPP requirements as part of their own obligations under the EU Digital Services Act framework.

The EU Battery Digital Product Passport is one of the most operationally demanding compliance requirements to hit e-commerce in years — but early movers have a genuine advantage. If your product catalogue includes e-bike batteries, power tool batteries, or any LMT-category product, the time to build your data infrastructure is now, not when the first enforcement notice lands. Ceendesis Battery Compliance is built to make that process manageable for growing e-commerce brands — without needing a compliance team the size of a large corporation. See what's included and get your DPP programme in place before the deadline closes.

Last verified: May 2026

Most foreign sellers find out about France's CITEO packaging rules the same way — a letter, a marketplace suspension notice, or a panicked Google search at 11pm. By that point, they're already behind. If you're shipping orders into France, whether through your own Shopify store, Amazon.fr, or any other channel, French law classes you as a "producer" of packaging waste. That means CITEO. That means registration, annual declarations, and contribution fees. This guide covers exactly what's required — practically, not theoretically.

France's CITEO EPR: what foreign sellers need to know

CITEO is the French Producer Responsibility Organisation (PRO) for packaging — the body authorised by the French government to collect EPR (Extended Producer Responsibility) contributions from companies that place packaged goods on the French market. Under France's AGEC Law (Loi Anti-Gaspillage pour une Économie Circulaire), any business — domestic or foreign — that sells packaged products to French consumers must either join an approved EPR scheme or set up an approved individual system for end-of-life packaging management. For the overwhelming majority of e-commerce sellers, joining CITEO's collective scheme is the practical route.

Here's the thing: the obligation doesn't start at some high-volume threshold. Unlike the UK's Plastic Packaging Tax, which only kicks in above 10 tonnes of plastic packaging per year, France's packaging EPR applies from unit one. Shipped a single order to a French address in a branded box last year? You're technically in scope. In practice, CITEO's enforcement focuses on sellers with meaningful volumes — but the legal obligation is absolute, and enforcement has been tightening steadily.

The fees you pay are calculated on the total weight and type of packaging materials you place on the French market annually — cardboard, plastic film, glass, steel, aluminium, and so on. CITEO publishes its tariff schedule each year. Getting registered isn't just about avoiding fines, either; it's increasingly a condition of selling through French retailers and marketplaces. If you're thinking about expanding seriously into EU markets, France is a non-negotiable compliance stop.

CITEO packaging EPR is one piece of a broader multi-country picture — we've covered the full scope in our guide to multi-country EPR packaging compliance.

Appointing your French Authorized Representative for CITEO

Non-resident companies — any business without a registered establishment in France — must appoint a French Authorized Representative (mandataire agréé) before registering with CITEO. This is a legal requirement, not optional admin tidying. Your representative signs documents on your behalf, acts as the point of contact with CITEO, and takes on legal responsibility for ensuring your registration and declarations are complete and accurate.

Finding a qualified representative isn't difficult, but you want someone with genuine CITEO experience rather than a generic accountancy firm that's never touched a packaging EPR declaration. Specialist EPR compliance consultancies operate in this space, and some packaging compliance platforms include representative services as part of their offering — worth checking before you pay separately for both.

And yes, your Authorized Representative needs actual data from you. They can't file a meaningful declaration without your packaging volumes — they're the legal conduit, not a magic box that generates numbers. That's why the data-gathering step (covered next) needs to happen in parallel with finding your representative, not after.

Once appointed, your representative handles the formal registration with CITEO, obtains your unique producer identification number, and becomes the entity CITEO contacts for invoicing, audits, and compliance queries. Keep them informed whenever your product range changes materially — new packaging formats, new materials, significant volume shifts. They can't flag what they don't know about.

Gathering packaging data for your CITEO declaration

Accurate packaging data is the foundation of every CITEO declaration — and it's where most foreign sellers hit their first real wall. CITEO doesn't want to know what you sold; it wants to know what packaging you placed on the French market, by material type and weight.

Specifically, you need to capture:

• Primary packaging — the packaging in direct contact with the product (a plastic bottle, a cardboard box the product sits in)
• Secondary packaging — packaging that groups primary units together (a shrink-wrapped multipack)
• Tertiary/transit packaging — outer packaging used for shipping (the cardboard mailer box or poly mailer you ship orders in)

For each packaging component, you need the material type (cardboard, paper, plastic — and the specific plastic polymer if possible), weight per unit in grams, and total units placed on the French market in the reporting year. Multiply weight per unit by units sold into France and you have your total tonnage per material type.

Here's where it gets messy for multi-channel sellers. If you're selling on both your Shopify store and Amazon.fr, you need to aggregate order data from both channels — and then isolate orders shipped to French delivery addresses. This is exactly the kind of problem that gets expensive fast when you're doing it manually in spreadsheets. A proper Shopify and Amazon inventory management setup with per-order destination tagging makes this extraction straightforward.

A practical example: say you sell a skincare set in a glass jar (45g) with a cardboard outer sleeve (12g) packed in a cardboard mailer box (85g). You shipped 3,200 orders to French addresses last year. Your total packaging weight placed on the French market works out to roughly glass 144kg, cardboard 310.4kg. Those figures go into your CITEO declaration — not your global sales totals, just France.

If you're also selling fashion products into France, you may have intersecting obligations under France's Refashion textile EPR scheme alongside CITEO — worth keeping the two compliance streams clearly separate.

Submitting your CITEO declaration: a step-by-step guide

The CITEO declaration process runs on an annual cycle — declarations for the previous calendar year are typically due in the first quarter of the following year. CITEO publishes its exact submission deadlines on its producer portal each year, and your Authorized Representative should be tracking these on your behalf.

The practical sequence looks like this:

1. Register as a producer via CITEO's online portal (your Authorized Representative does this on your behalf if you're non-resident). You'll receive a unique producer number.
2. Compile your packaging data by material type and total weight for the reporting year — as described in the previous section.
3. Complete the CITEO declaration form in the producer portal, entering weights by material category. The portal calculates your contribution fee based on CITEO's published tariff schedule for that year.
4. Review and validate the declaration — your Authorized Representative will countersign or submit as mandated.
5. Pay the contribution fee by the invoiced deadline. CITEO invoices after declaration submission.

Sounds straightforward. But the data aggregation step — pulling French order volumes from multiple channels, matching them to SKU-level packaging specs, totalling by material — is where the hours disappear if you're doing it manually. Brands running specialist EPR packaging compliance software can automate most of this: the platform pulls order data, applies your packaging weight specs per SKU, filters by destination country, and produces declaration-ready output.

When we were running our own brands, the first time we tried to compile a CITEO-ready packaging report manually it took the better part of two days — most of which disappeared reconciling Shopify export formats with Amazon transaction reports, then manually summing by delivery country. That's not a workflow you want repeated every January.

Below is a reference table comparing the key CITEO declaration requirements against what you'd typically need for Germany's VerpackG and the UK's Plastic Packaging Tax (PPT) — useful if you're managing compliance across multiple markets.

Maintaining compliance and avoiding penalties

Non-compliance with CITEO's packaging EPR carries real consequences — administrative fines, potential injunctions against selling into the French market, and marketplace enforcement, where platforms are now required to verify seller compliance status. Amazon.fr has been actively requesting EPR compliance documentation from third-party sellers since 2022. Ignore it long enough and your listings get restricted. That's the last thing your ops team wants to be dealing with mid-peak.

But compliance isn't a one-time event. It's an annual cycle. Here's what ongoing maintenance actually looks like:

• Keep your packaging specs current. If you change your packaging — new mailer box, switch from plastic to paper void fill, updated product packaging — update your SKU-level packaging records immediately. Outdated specs produce incorrect declarations.
• Track French order volumes continuously. Don't wait until Q1 to start reconstructing last year's French shipments. A running total by destination country is far easier to work with than a year-end export you have to reverse-engineer.
• Watch CITEO's annual tariff updates. Contribution fee rates are reviewed and published annually. Budget accordingly — fees have generally trended upward as France expands its recycling infrastructure targets.
• Keep your Authorized Representative in the loop. New product lines, new packaging suppliers, material shifts — communicate these promptly. They can't flag what they don't know about.

Frankly, most brands overcomplicate the maintenance side. The heavy work is upfront: getting registered, mapping your packaging specs accurately, and setting up data flows. Once that infrastructure is in place, the annual declaration becomes a report run, not a crisis.

If you're managing compliance alongside complex multi-channel operations — wholesale and multi-channel inventory being the most common scenario we see — it pays to centralise your data. An inventory management platform that holds per-SKU packaging data and can filter order history by destination country is the practical foundation for CITEO reporting, not just stock control. We cover this kind of integrated ops thinking in our 7-figure DTC operations stack guide.

For fashion brands, the compliance picture is layered — CITEO for packaging on top of Refashion obligations on the garments themselves. Our sustainable operations stack for fashion brands covers how to handle both without duplicating effort.

Frequently asked questions

Do foreign companies need a French authorized representative for CITEO packaging EPR?

Yes — non-resident companies selling packaged goods into France must appoint a French Authorized Representative (mandataire agréé) before registering with CITEO. This representative signs documents on your behalf, submits declarations, and acts as the legal point of contact with CITEO. You cannot self-register as a non-resident company without one.

What specific packaging data is required for CITEO declarations by e-commerce sellers?

CITEO declarations require the total weight (in kg or tonnes) of each packaging material type placed on the French market in the reporting year — covering primary, secondary, and transit packaging. You'll need material categories (cardboard, paper, glass, plastic by polymer type, steel, aluminium, and other), the weight per packaging unit in grams, and total units shipped to French addresses. Multiplying per-unit weight by French order volume gives you the tonnage figures CITEO needs.

How often do e-commerce sellers need to report packaging to CITEO in France?

CITEO declarations are submitted annually, covering the previous calendar year. Declarations for 2025 activity are typically due in early 2026 — your Authorized Representative should confirm the exact deadline from CITEO's producer portal each year. Unlike the UK's Plastic Packaging Tax, which requires quarterly returns, CITEO runs on a single annual reporting cycle.

What are the consequences of non-compliance with France's CITEO regulations?

Non-compliance can result in administrative fines under France's AGEC Law, injunctions against selling on the French market, and marketplace enforcement actions — Amazon.fr and other platforms have been actively requiring EPR compliance documentation from sellers. Beyond legal penalties, failing to register leaves you unable to provide the compliance certificates French retailers and distributors increasingly demand.

Can e-commerce platforms like Amazon or Shopify handle my CITEO reporting for sales into France?

No — Amazon and Shopify don't manage CITEO registration or declarations on your behalf, and legal responsibility stays with you as the producer. Some marketplaces assist with compliance verification and may collect EPR fees from sellers in specific categories, but registering, appointing a representative, and filing declarations is your obligation. Specialist packaging compliance software can automate the data extraction and declaration preparation steps, but doesn't remove your legal responsibility either.

CITEO compliance is genuinely manageable once you've set the foundations — the right representative, clean per-SKU packaging data, and a reliable way to extract French order volumes from your channels. The brands that struggle are the ones treating it as a once-a-year emergency rather than a background process. If you're ready to stop rebuilding your packaging dataset from scratch each January, see how Ceendesis Packaging Compliance handles it — and if you're also juggling inventory across Shopify, Amazon, and other channels, explore what IMS can do alongside it.

Last verified: May 2026

Here's the problem most Shopify sellers hit within their first month of using Xero: the payout that lands in your bank account doesn't match anything in your sales reports. That's not a bug. Shopify payouts are net deposits — Shopify deducts transaction fees, processing fees, refunds, and chargebacks before sending the money. A £5,000 sales day might produce a £4,800 payout, and unless Xero knows about the £200 difference, your books are wrong from day one.

Reconciling that gap means breaking each payout down into its components — gross sales, Shopify fees, refunds, taxes — and posting each piece to the correct account in Xero. Add multi-currency orders, partial refunds, and app fees and it gets messy fast. Still solvable, though, and this guide covers every method available in 2026.

Unreconciled payouts compound. Leave one month's mess unresolved and you're cleaning up two months next time. For anyone running a 7-figure DTC operations stack or a lean solo operation, getting this right early is the kind of unsexy decision that saves you a very painful audit conversation later.

Before you start

• Active Shopify store with admin access
• Active Xero organisation with appropriate user permissions
• A Xero subscription plan that supports multi-currency if you sell internationally
• Chart of accounts set up in Xero to handle sales, fees, refunds, and taxes

That last point matters more than it sounds. Your chart of accounts structure directly affects your reporting accuracy. At minimum, you want dedicated accounts for: Shopify Sales, Shopify Fees, Shopify Refunds, and a Shopify Clearing Account. The clearing account is where the work happens — it receives the gross payout breakdown and nets to zero once the bank deposit is matched. It's a standard e-commerce bookkeeping principle, and it keeps everything traceable.

Methods at a glance

Method 1: Manual export/import

The brute-force approach. Shopify's payout reports, a spreadsheet, and manual journal entries in Xero — nothing else. The time cost grows with every payout, so if you're processing more than a handful per month this will eat your week. Use it to understand what reconciliation actually involves, or as a stop-gap while you get something better configured. Honestly, doing this manually once is worth it — you'll understand the numbers in a way that makes every automated method easier to trust.

1. Export your payout report from Shopify. In Shopify Admin, go to Finances > Payouts. Select a payout and click Export to download the transaction-level CSV. This file lists every order, refund, adjustment, and fee included in that payout. Expected result: a CSV with line-level transaction data.
2. Reconcile the CSV totals. Sum the gross sales, subtract all fees (transaction, processing, app), subtract refunds, and verify the net matches the bank deposit figure. If they don't match, look for chargebacks or reserve deductions in the Shopify Payments section of your admin. Expected result: a confirmed net figure that matches the bank deposit.
3. Create a manual journal entry in Xero. In Xero, go to Accounting > Journal entries > New journal. Debit your Shopify Clearing account for the gross sales amount. Credit individual accounts for fees, refunds, and taxes. The clearing account balance should then equal the net payout. Expected result: the journal entry posts without errors and the clearing account balance matches the bank deposit.
4. Match the bank deposit in Xero. Go to Accounting > Bank accounts, find the Shopify payout deposit, and match it to the clearing account entry. Expected result: the transaction is reconciled and the clearing account nets to zero for that payout period.
5. Repeat for each payout. Shopify typically pays out on a rolling schedule — daily if you're on Shopify Payments. That means this process repeats frequently. Consider batching by week or month if volume is low.

You can also sync Shopify orders to Google Sheets first if you want running summaries before touching Xero — useful for brands doing their own month-end checks.

Method 2: Xero's native Shopify app

Xero builds and maintains an official Shopify integration — the Shopify Integration by Xero. It connects the two platforms directly and handles the most common sync scenarios automatically. Think of it as a transaction pipe rather than a full accounting engine — clean, functional, but deliberately simple. For straightforward stores it removes most of the manual work. The Shopify Help documentation and Xero Central setup guide both cover the connection steps in detail.

1. Install the Shopify Integration by Xero from the Xero App Store. In Xero, go to App Store and search "Shopify Integration by Xero". Click Get this app. Expected result: you're redirected to an authorisation screen.
2. Connect your Shopify store. Enter your Shopify store URL and click Connect. Authenticate with your Shopify admin credentials when prompted. Expected result: the integration dashboard shows your store as connected.
3. Map your accounts. The integration will ask you to map Shopify transaction types (sales, fees, refunds, taxes, shipping) to Xero accounts. Match these to the accounts you set up in your chart of accounts. Each transaction type needs its own account — generic mappings produce messy books and harder month-ends. Expected result: each transaction type has a corresponding Xero account, with nothing left unmapped.
4. Set your sync start date. Choose the date from which you want transactions to sync. Don't pick a date before your Xero organisation start date. Expected result: only transactions from your chosen date forward will be imported.
5. Run the initial sync and review. Let the integration import your first batch of transactions. In Xero, go to Accounting > Bank accounts and review the imported items against your actual bank feed. Expected result: Shopify payouts appear as matched or suggested matches in your bank reconciliation screen.
6. Reconcile remaining unmatched items. The native app summarises transactions — it may not split every fee line individually. For any unmatched items, create manual adjustments or journal entries as needed. Expected result: all payout-period items reconcile cleanly.

Method 3: Connector tool

For stores that need granular control — per-fee-type categorisation, COGS tracking, tax jurisdiction splitting, or multi-currency payout handling — a dedicated connector tool does what the native app doesn't. These tools sit between Shopify and Xero, parse the raw transaction data, and post categorised entries to Xero automatically. They're particularly useful if you're running multiple fulfilment and shipping workflows with variable fee structures.

1. Choose and install a connector app. Search the Xero App Store or Shopify App Store for apps that specifically handle Shopify-to-Xero payout reconciliation. Look for ones that explicitly support payout-level (not just order-level) syncing, and that handle fees, refunds, and chargebacks as separate line items. Expected result: the app is installed in both your Shopify admin and your Xero organisation.
2. Authorise both platform connections. The connector will ask you to authenticate with both Shopify and Xero. Grant the required permissions — typically read access to Shopify Payments data and write access to Xero bank transactions and journal entries. Expected result: both connections show as active in the connector dashboard.
3. Configure your account mapping. Map each transaction category the connector identifies (gross sales, transaction fees, processing fees, refunds, partial refunds, chargebacks, adjustments, gift cards) to your corresponding Xero accounts. Specific mappings matter here — every category needs a dedicated Xero account target, not a catch-all. Expected result: every category has a dedicated Xero account target.
4. Set up your clearing account workflow. Configure the connector to post gross transaction amounts to your Shopify Clearing account and the net deposit to your bank account. The clearing account should zero out with each payout cycle. Expected result: the clearing account balance matches the outstanding payout at any point in the cycle, and zeros on deposit.
5. Enable multi-currency settings if applicable. If you process orders in multiple currencies, configure the connector to use Xero's exchange rate or a fixed rate per payout. Make sure your Xero plan supports multi-currency before enabling this. Expected result: foreign-currency transactions post with the correct exchange rate and conversion fees are captured separately.
6. Review the first automated sync. After the connector processes its first payout, cross-reference the Xero entries against your Shopify Payments payout report. Expected result: every line in the payout report maps to a corresponding Xero entry, and the totals match to the penny.

Method 4: Ceendesis Accounting

Ceendesis Accounting is a fully managed reconciliation service built for multi-channel e-commerce brands. Rather than giving you another tool to configure and maintain, it handles the entire reconciliation process — parsing settlement flat files from Shopify (and Amazon, eBay, and Walmart if you sell there too), splitting payouts into their components, and posting clean, categorised entries into Xero or QuickBooks. If you're running Shopify alongside Amazon, the per-channel COGS tracking and tax engine are particularly useful — you get one consolidated view without manually aggregating two separate workflows. Worth noting: Ceendesis Accounting is built around Xero and QuickBooks. There's no Sage support yet, so if your organisation runs on Sage, this isn't your method.

1. Contact the Ceendesis team. Visit ceendesis.com/accounting and submit an onboarding enquiry. A team member will confirm scope (which channels, which accounting platform, historical data requirements). Expected result: a confirmed onboarding scope and start date.
2. Grant read access to your Shopify Payments data. You'll be asked to provide API credentials or grant a staff account with the necessary permissions. Ceendesis uses Shopify's SP-API for full settlement flat-file parsing. Expected result: the team confirms data access is working and can pull historical payout data.
3. Review and approve your account mapping. Ceendesis will propose a chart of accounts mapping based on your existing Xero setup — or help you build one if it's not yet structured for e-commerce. You review and approve before anything posts to Xero. Expected result: a signed-off mapping document covering sales, fees, refunds, taxes, and any channel-specific adjustments.
4. Validate the first reconciliation run. Ceendesis processes an initial batch and shares a reconciliation summary for your review. Cross-check against one or two Shopify payout reports manually to confirm accuracy. Expected result: every payout in the test batch matches the bank deposit, with all components categorised correctly.
5. Hand off ongoing reconciliation. Once the initial run is validated, Ceendesis handles the process on your agreed cadence (weekly or monthly). Expected result: Xero is updated without you touching it, and your books are reconciliation-ready at month end.

Common errors and how to fix them

Timing mismatches between payout dates and bank deposit dates

Shopify processes payouts on a rolling schedule, but the deposit may take one to three business days to clear in your bank. This creates a gap: the payout is "sent" on Monday but appears in your bank on Wednesday. If you're matching on date in Xero, the entries won't align. Fix: use the actual bank deposit date (not the Shopify payout date) as your Xero transaction date, or use a clearing account that absorbs the timing difference. Don't force a date match — let the clearing account do the work.

Shopify fees not categorised correctly

Transaction fees, payment processing fees, and app subscription fees are all different things — but they're often lumped together or missed entirely. Each type should map to a distinct Xero account so you can see what you're actually paying Shopify. If you're using the native app and fees aren't splitting correctly, check your account mapping configuration. If you're doing this manually, cross-reference the payout CSV's "fee type" column against your journal entries.

Refunds and chargebacks netted from payouts cause reconciliation gaps

A chargeback or refund in the same payout period reduces the net deposit — but if your Xero entries only record gross sales and fees, the bank deposit won't match. Fix: post refunds and chargebacks as separate negative entries (or credits) to your sales account, not absorbed silently into the net figure. If you're using a connector tool, verify it handles partial refunds as well as full refunds — partial refunds are a common gap. For managing the upstream returns process, the best Shopify returns apps can help reduce the volume of manual refund adjustments you're dealing with in the first place.

Multi-currency exchange rate discrepancies

If you accept orders in USD, EUR, or other currencies but your Xero organisation's base currency is GBP, the exchange rate Shopify uses at time of sale may differ from the rate Xero applies when you import transactions. That difference creates small variances that won't reconcile cleanly. Fix: decide on a consistent exchange rate source — either Xero's daily rate or a fixed monthly rate — and apply it uniformly across all entries for the period. Document your policy so your accountant knows what to expect. This is one area where a connector tool or managed service earns its keep, since they handle rate normalisation automatically.

Frequently asked questions

How do I account for Shopify fees in Xero?

Create dedicated Xero accounts for each fee type — transaction fees, payment processing fees, and subscription/app fees — then map them separately during reconciliation. Whether you're doing this manually via journal entry or using a connector tool, each fee type should post to its own account so your P&L reflects actual Shopify costs accurately, not a single blended "Shopify expense" line.

Why are my Shopify payouts not matching my sales?

Because Shopify payouts are net deposits — Shopify deducts fees, refunds, chargebacks, and any reserve amounts before the money reaches your bank. A day's gross sales and the resulting payout will almost never be the same figure. Reconciliation means accounting for all those deductions explicitly, not finding a way to make the two numbers match directly.

Does Xero integrate directly with Shopify?

Yes — Xero maintains an official native integration called "Shopify Integration by Xero", available from both the Xero App Store and the Shopify App Store. It handles basic transaction syncing but isn't designed for granular fee-level reconciliation — for that, a connector tool or managed service gives you more control.

How do I automate Shopify reconciliation in Xero?

Three routes: use the native Xero-Shopify app for a basic set-and-forget sync, use a dedicated connector tool for granular automated categorisation, or use a managed service like Ceendesis Accounting if you want zero internal overhead. The right choice depends on how complex your fee structure is and whether you're reconciling Shopify alone or alongside other channels like Amazon.

Which method should you use?

Start manual. Once. It's tedious — genuinely — but you'll finish knowing exactly what the numbers mean, what the fees represent, and where reconciliation gaps actually come from. That knowledge is worth far more than the two hours it takes. After that, setting up automation stops being an act of faith.

For most single-channel Shopify stores with straightforward fee structures, Xero's native integration is probably enough — quick to set up, low maintenance, covers the common cases. But if you're seeing persistent reconciliation gaps, dealing with heavy refund volumes, or selling in multiple currencies, a connector tool will save you hours of monthly debugging.

And if you're running Shopify alongside Amazon, eBay, or Walmart — or you simply don't want to own the reconciliation process at all — the managed approach makes more sense. Particularly for brands building out a broader EU expansion operations stack, where channel complexity and tax obligations stack up quickly, having clean per-channel financials in Xero from day one is worth more than the cost of maintaining it yourself. If you're also syncing data across other systems, our guides on connecting Amazon Seller Central to Google Sheets and connecting Amazon to QuickBooks cover the adjacent workflows.

Last verified: May 2026

Selling into Europe isn't just "shipping to more postcodes." The EU is a collection of overlapping regulatory frameworks, each with its own compliance calendar, language requirements, and payment culture. A brand that's nailed its UK or US operations can still run into serious trouble at the German customs portal or the French CITEO registration page.

This stack is for e-commerce brands — most likely running on Shopify and Amazon — that are either preparing for EU expansion or already selling into Europe and feeling the operational strain. We've built it around the categories that actually break: payments, VAT, compliance, customer support, returns, analytics, and localisation. If you're looking for the broader DTC picture, our 7-figure DTC operations stack covers the full foundation.

One honest caveat upfront: the EU is not a single market in any operational sense. As the European Parliament acknowledged in early 2026, administrative fragmentation remains a genuine barrier for cross-border sellers. No software stack eliminates that entirely — but the right tools reduce it from a crisis to a manageable process.

Payment gateways

Europe's payment landscape is fragmented by design. Cards dominate in some markets, local schemes in others — iDEAL in the Netherlands, Bancontact in Belgium, SOFORT across German-speaking markets. Payment preferences genuinely vary by country. A gateway that only handles Visa and Mastercard will quietly kill your conversion rate in markets where those aren't the default. You need a processor that either natively supports local methods or lets you bolt them on.

Stripe

Stripe is the default choice for most Shopify-based brands entering Europe — developer-friendly, well-documented, and capable of handling the payment complexity EU expansion creates without a separate integration for every new market.

Strengths

• Automated VAT and GST calculation via Stripe Tax, which cuts the manual overhead of collecting the right rate across multiple EU jurisdictions
• Stripe Radar provides fraud detection that's particularly useful when you're accepting orders from unfamiliar geographies
• Supports recurring billing — useful if you're running any kind of subscription or pre-order model alongside your EU launch

Best fit

Businesses of all sizes looking to accept payments, build flexible billing models, and move money across borders. Bear in mind that Stripe's core payment processing incurs per-transaction fees, so model your margins at volume before committing.

Adyen

Adyen is the enterprise-tier option — a single platform for online, in-store, and in-app payments with genuine global acquiring capability and multi-currency settlement built in from the start.

Strengths

• Unified commerce across online, in-store, and in-app channels — relevant if your EU expansion includes any wholesale or pop-up retail component
• RevenueProtect fraud tooling is more configurable than most mid-market solutions, which matters when you're dealing with unfamiliar shipping addresses and new customer cohorts
• Native integrations with Shopify, Magento, BigCommerce, and Salesforce Commerce Cloud mean less custom engineering to get live

Best fit

Scaling businesses with high transaction volumes and genuine multi-channel operations. Adyen typically requires a minimum monthly invoice, so it's not the right call for brands still testing EU demand at low volumes.

Tax & VAT compliance

VAT is where EU expansion gets expensive fast if you don't automate it early. The EU-wide €10,000 threshold for distance sales means most brands exceed it quickly, triggering multi-country VAT registration obligations. The One-Stop Shop (OSS) system simplifies filing somewhat, but it doesn't remove the need to track distance selling thresholds, monitor which countries you've triggered, or handle Import One-Stop Shop (IOSS) for sub-€150 imports. For a detailed breakdown of multi-country compliance obligations beyond VAT, our packaging EPR guide covers the adjacent territory.

Sovos

Sovos is a comprehensive global tax compliance platform covering sales tax, VAT, excise, and e-invoicing — built for businesses with complex, multi-jurisdiction tax obligations and significant transaction volumes.

Strengths

• Global tax determination across sales, use, VAT, and excise — covers the full EU spectrum, including countries with real-time e-invoicing mandates
• Automated filing and remittance removes the manual calendar-watching that causes most VAT penalties
• Sovi® AI provides guided tax automation — useful for compliance teams handling edge cases across multiple EU markets at the same time

Best fit

Large global businesses across retail, manufacturing, and financial services that need to manage complex tax compliance and regulatory reporting worldwide. The modular design means the complete solution may require multiple modules for full functionality — factor that into your evaluation.

Taxually

Taxually is an automated VAT and sales tax platform with a sharp focus on e-commerce, including native integrations with the marketplaces and platforms that growing brands actually use.

Strengths

• Instant VAT registration and deregistration — critical when you're moving fast across new EU markets and need to stay compliant without a six-week delay
• Distance selling threshold monitoring, so you know exactly when you've triggered an obligation in a new country before the filing deadline hits
• EcoTax module handles environmental tax compliance — useful if your products carry EPR obligations alongside standard VAT requirements

Best fit

E-commerce businesses, accounting providers, and enterprises automating global VAT and US sales tax compliance. No public pricing is listed on the Taxually website, so you'll need to contact them for a quote.

Inventory & compliance

Multi-channel inventory is the operational backbone of any EU expansion. Selling into Germany, France, and the Netherlands at the same time — across Amazon EU, your own Shopify store, and potentially a marketplace like Bol — means stock visibility needs to be real-time and accurate. Beyond inventory, EPR compliance is now a hard market-access requirement in most EU countries. From 2026 onward, any business placing packaging on the EU market must systematically record quantities and material types. And if you don't have a physical EU presence, you'll need an Authorised Representative in each country you sell into by August 12, 2026. Our EPR packaging obligations calculator is a good starting point if you're not sure what you owe.

Ceendesis

Ceendesis combines multi-channel inventory management, EPR compliance (packaging, textiles, and batteries), and marketplace-to-accounting sync in a single platform — built specifically for brands operating across multiple sales channels and EU markets.

Strengths

• Inventory, EPR compliance, and marketplace-to-accounting sync in one platform — no need for three separate integrations to cover what EU expansion demands
• Built for brands selling on Shopify, Amazon, eBay, Walmart, and TikTok Shop — covers the channel mix most growing brands are actually running
• Native Xero and QuickBooks reconciliation for marketplace payouts, which keeps your EU revenue clean in your accounting system without manual CSV imports

Best fit

Built for brands on 2+ marketplaces — overkill for single-channel Shopify-only stores. If you're selling into the EU across Amazon and Shopify at the same time and need EPR compliance handled alongside inventory, this is where the platform earns its keep. Fashion brands should also see our sustainable operations stack for fashion brands for the full textile compliance picture.

Customer support

EU customers expect support in their own language. That's not a generalisation — it's a consistent finding from brands that launched in Germany or France and tried to get away with English-only support. Beyond language, EU consumer protection rules give customers strong return and refund rights, which means your support team will handle more policy-driven queries than you're used to. The tooling needs to handle volume, multilingual macros, and Shopify order actions without agents switching between five tabs.

Gorgias

Gorgias is the most Shopify-native helpdesk on the market — built specifically for e-commerce, with the ability to cancel, refund, discount, and edit orders directly from the support thread without leaving the tool.

Strengths

• One omnichannel inbox covering email, chat, SMS, WhatsApp, Instagram, and Facebook — EU customers use a wider range of contact channels than most US brands expect
• AI Agent handles automated ticket resolution, which matters when your support volume spikes post-EU launch and you're not yet staffed for it
• Revenue attribution reporting ties support interactions to conversion — useful for proving the ROI of localised support investment to your finance team

Best fit

E-commerce businesses looking to automate customer support, centralise communications, and drive sales through personalised interactions. Note that the AI Agent is an add-on billed separately per resolved conversation, on top of the standard helpdesk fee — worth modelling before you enable it at scale. For more on returns-related support workflows, see our roundup of the best Shopify returns apps.

Zendesk

Zendesk is the enterprise-standard support platform — broader, more configurable, and better suited to teams handling high ticket volumes across large organisations with dedicated support functions.

Strengths

• Omnichannel ticketing across email, chat, phone, social, and messaging apps — covers the full contact surface for EU markets including platforms like WhatsApp that are standard in Southern Europe
• Self-service knowledge base and Help Centre with multilingual support on higher tiers — lets you build out localised FAQs per market without duplicating your support team
• Zendesk Explore provides detailed reporting and analytics, which matters when you're trying to understand which markets generate the most support load post-expansion

Best fit

Support teams handling high ticket volumes across large organisations. Advanced AI features and certain add-ons are often locked behind higher tiers or incur additional costs — check the current tier structure before committing.

Returns management

EU consumer law gives buyers strong return rights — in most cases, 14 days minimum with no reason required for distance purchases. That's not negotiable. What you can control is how efficiently your returns process runs and how often you convert a return into an exchange rather than a refund. For brands shipping from outside the EU, the removal of the €150 duty-free threshold from July 2026 also changes the economics of returned goods — factor that into your reverse logistics planning.

Loop Returns

Loop Returns is an exchange-first returns platform built for Shopify brands — designed to retain revenue by steering customers toward exchanges and store credit rather than straight refunds.

Strengths

• Exchange-first return flow with Shop Now and Instant Exchange — lets customers swap for a different size or product before the original return is processed, which is particularly valuable in EU apparel markets
• Fraud detection built into the returns workflow — important when you're dealing with new customer cohorts in unfamiliar markets
• Self-service returns portal reduces agent handling time on straightforward return requests

Best fit

High-volume Shopify brands focused on post-purchase operations. Order Tracking pricing is based on the plan selected and monthly shipment volume, with additional per-shipment fees for volumes beyond the monthly estimate — read the pricing page carefully before projecting costs at EU scale.

AfterShip Returns

AfterShip Returns is a returns management platform that works across Shopify, BigCommerce, and WooCommerce — a better fit for brands running a multi-platform stack rather than pure Shopify.

Strengths

• Branded returns page keeps the customer experience consistent across markets without requiring custom development work
• Real-time return shipment tracking reduces inbound "where's my refund?" queries, which tend to spike when customers are dealing with international return shipping
• Incentivised exchanges and store credits give you the revenue-retention mechanics even at the Essentials tier

Best fit

E-commerce brands looking to automate and optimise returns and exchanges across multiple platforms. All pricing tiers cap the number of returns per year, with extra returns incurring an additional fee — model your expected EU return volume against the tier limits before selecting a plan.

Analytics

GDPR compliance makes your analytics choices non-trivial in Europe. Tools that rely on third-party cookies or transfer data outside the EU without appropriate safeguards can create compliance exposure. That's not theoretical — EU data protection authorities have issued fines for analytics implementations that couldn't demonstrate GDPR compliance. Choose tools where data residency and consent management are first-class features, not afterthoughts.

Matomo

Matomo is a privacy-first analytics platform with a self-hosted option that gives you full data ownership — which makes GDPR consent management substantially simpler, because you're not transmitting data to a third-party server in a non-EU jurisdiction.

Strengths

• Full data ownership — self-hosted deployments mean no data leaves your infrastructure, which simplifies your GDPR data processing records considerably
• E-commerce analytics and goal conversion tracking built in — covers funnel visibility without requiring a separate product analytics tool
• Real-time data updates, which matter when you're monitoring conversion rates across newly launched EU market campaigns

Best fit

Organisations seeking privacy-first web analytics with full data ownership and GDPR compliance. The self-hosted version requires you to manage your own servers and infrastructure — factor in the engineering overhead if your team isn't set up for that.

Mixpanel

Mixpanel is a product analytics platform focused on user behaviour, conversion funnels, and retention — more suited to understanding how customers move through your storefront than tracking aggregate traffic volumes.

Strengths

• Funnel analysis lets you identify exactly where EU customers drop off during checkout — particularly useful when you're testing localised checkout flows for new markets
• Cohort analysis helps you understand retention differences between, say, German customers and French customers who came in through different acquisition channels
• Session Replay and Heatmaps on higher tiers give qualitative context to the quantitative funnel data

Best fit

Teams that need to track user behaviour, measure conversions, and improve retention at the product level. The free tier is limited to 5 saved reports and 10,000 monthly session replays — useful for early-stage EU testing, but you'll outgrow it quickly at meaningful traffic volumes.

Localisation

Localisation is the part of EU expansion that most brands underinvest in until it starts visibly hurting conversion. Running a German-language store with machine-translated product descriptions and no German-language customer support is better than nothing — but not by much. The good news is that modern localisation tooling has made the initial setup fast. Getting your Shopify store into four EU languages used to take weeks of development work. With the right tool, it's a weekend project.

Weglot

Weglot is a no-code translation platform that detects content automatically, handles multilingual SEO via language-specific URLs and hreflang tags, and integrates directly with Shopify and most other major e-commerce platforms.

Strengths

• No-code installation — a brand founder can get their Shopify store translating into three EU languages in an afternoon, without waiting on a developer
• Multilingual SEO with proper hreflang implementation means your translated pages actually get indexed and ranked in local search results, not just served to existing visitors
• Visual in-context editor lets you review and edit translations on the live storefront rather than in a spreadsheet — which dramatically reduces review time for non-technical team members

Best fit

Small to mid-sized businesses that need a fast, no-code solution to make their websites multilingual and SEO-ready. The free tier is limited to 2,000 translated words and one language — fine for testing, not enough for a full EU storefront.

Crowdin

Crowdin is a translation management and localisation platform built for teams that need structured translation workflows — more appropriate when you're managing translators, maintaining translation memory across large content volumes, or localising software and mobile apps alongside your storefront.

Strengths

• Translation Memory reuses previously approved translations across new content — which cuts both cost and inconsistency as your EU content library grows
• Automated QA checks catch common translation errors before they reach your storefront or customer communications
• Customisable workflows let you set up review and approval stages — essential if you're working with external translators across multiple EU languages at the same time

Best fit

Teams and businesses managing translation workflows for software, web, and mobile applications at scale. The free tier (Crowdin Open) restricts access to advanced integrations, machine translation engines, and priority support — the paid tiers are where the workflow management value actually lives.

The stack at a glance

Frequently asked questions

What software do I need to sell online in Europe?

At minimum: a payment gateway that supports EU local payment methods (Stripe or Adyen), a VAT compliance tool that monitors distance selling thresholds and handles OSS/IOSS filing (Taxually or Sovos), and a localisation solution for your storefront (Weglot gets most brands live fastest). If you're selling packaged goods, textiles, or battery-containing products, you'll also need EPR compliance coverage — that's where Ceendesis fills the gap for multi-channel brands. For shipping, our shipping software guide covers the carrier and label side of EU fulfilment in more detail.

How do DTC brands handle EU VAT and customs?

Most growing DTC brands use the Import One-Stop Shop (IOSS) for shipments into the EU from outside, which lets you register in a single EU member state and pay VAT on all eligible EU sales through one portal. For distance sales within the EU — if you're holding stock in an EU warehouse — the domestic OSS scheme handles multi-country VAT filing. What changes from July 2026 is customs duty: the €150 de minimis exemption is being removed, meaning every shipment from outside the EU now attracts duty regardless of value. That makes landed cost calculation at the point of sale non-negotiable for maintaining accurate margins and avoiding delivery surprises for your customers.

What are the biggest operational challenges of expanding an e-commerce brand to Europe?

In our experience, three things catch brands off guard. First, VAT compliance at scale — the EU's distance selling thresholds are easy to exceed quickly, and the penalties for late registration in some member states are significant. Second, EPR obligations — Germany's VerpackG, France's CITEO, and the UK's Plastic Packaging Tax all have different registration timelines, reporting formats, and fee structures. Brands that assumed EPR was a future problem have found themselves deregistered from Amazon EU marketplaces. Third, fragmented fulfilment — holding stock in two or three EU nodes dramatically improves delivery speed and cuts per-shipment costs, but it requires real-time multi-warehouse inventory visibility to avoid overselling. For a deeper look at the inventory side, our guide on syncing Shopify inventory to Amazon FBA covers the mechanics of multi-node stock management.

Where to start

If you're pre-launch in Europe, the essential tier is: payment gateway, VAT compliance, and localisation. Get those three working before you worry about anything else. Returns management becomes critical once you're past a few hundred EU orders a month — EU consumer law means your return rate will likely be higher than you're used to, and manual processing doesn't scale. Analytics (specifically Matomo if GDPR simplicity matters to you) should go in early, because EU market data from month one is worth more than retrospective analysis six months later.

Ceendesis slots in when you're operating across two or more channels and need inventory, EPR compliance, and accounting reconciliation handled in one place rather than stitched together across three separate tools. For fashion brands specifically, the EPR picture is more complex — Refashion in France, the Dutch UPV, and incoming EU Digital Product Passport requirements all add layers that warrant their own stack consideration. Our Refashion eco-modulation guide and the sustainable operations stack for fashion brands are the right starting points for that conversation. And if you're still building out the foundational purchase order and receiving workflows before EU expansion, our PO workflow automation guide covers what to fix first.

Screenshots are from each tool's public pricing or features page, captured May 2026. We are not affiliated with any third-party tool listed unless explicitly noted.

Last verified: May 2026

Running Shopify and Dynamics 365 Business Central as separate systems is a slow leak. Orders land in Shopify, someone manually keys them into Business Central, inventory counts fall behind, and eventually a customer buys something you don't actually have. It's a familiar story. The fix — connecting the two platforms — sounds simple enough, but the method you pick determines how much maintenance you're signing up for long-term.

Microsoft's own documentation puts it plainly: synchronise orders, stock, and customer information to fulfil orders faster and serve customers better. That's the right frame. This guide covers all three realistic integration paths — native connector, third-party platform, and direct API — with step-by-step instructions for each, plus the errors you'll actually hit along the way.

Whether you run a single Shopify store or manage multiple storefronts feeding one ERP, there's a method here that fits. The right choice depends on your Business Central deployment, your tolerance for ongoing maintenance, and how much custom field mapping you need. We'll get into all of it.

Before you start

• A Shopify account and an active online store.
• A Microsoft Dynamics 365 Business Central account.
• The Shopify Connector app must be installed in Business Central.
• The user must have the Shopify – Admin (SHPFY – ADMIN) permission set in Business Central.

Methods at a glance

Method 1: Native Shopify Connector for Business Central

This is the cleanest option if you're on Business Central SaaS. Microsoft built the connector into the product — it's not something you cobble together from add-ons; it's a first-party integration maintained alongside Business Central updates. As of early 2026, it runs on the January 2026 Shopify API release, which means expanded metafield support and more granular payout data are now available out of the box.

1. Open Business Central and use the search bar (the magnifying glass icon or Alt+Q) to find Shopify Shops.
2. Click New to create a new shop connection. Enter a short code (e.g. MAIN-UK) — this is Business Central's internal identifier for the store, not the Shopify URL.
3. Enter your Shopify store URL in the Shopify URL field (e.g. yourstore.myshopify.com). Business Central will prompt you to authenticate via OAuth.
4. Authorise the connection in the Shopify authentication window that opens. You'll need to be logged into Shopify as a store owner or have the relevant API permissions. Click Install app to confirm. The Shopify App Store listing confirms what permissions are requested.
5. Configure sync settings in the Shopify Shop Card that appears. Here you'll define: which Business Central location maps to which Shopify location, how inventory is calculated (committed stock, available stock, or a formula), and whether Business Central or Shopify is the master for pricing.
6. Set up customer and order sync by scrolling to the Orders and Customers sections of the Shop Card. Decide whether incoming Shopify orders create new BC customers automatically or map to a default customer (useful for B2C where individual customer records aren't needed).
7. Run an initial product sync by navigating to Shopify Products and clicking Sync Products from Shopify. Expect a few minutes for large catalogues. Check the resulting list — each product line should show a mapped BC item number.
8. Run an initial inventory sync by going to Shopify Inventory and clicking Sync Inventory to Shopify. Business Central pushes current stock levels to Shopify. Verify in Shopify admin that quantities updated correctly for two or three SKUs.
9. Enable automatic background sync by setting the Sync Items, Sync Orders, and Sync Inventory job queues to Active in Business Central's Job Queue Entries. These run on a schedule (typically every 30 minutes, configurable).
10. Place a test order in your Shopify store (use a discount code to zero out the charge if needed) and confirm it appears in Business Central under Shopify Orders within one sync cycle.

If your operations extend beyond a single storefront — say you run a UK store and a German store separately — repeat this process for each. Business Central supports multiple Shopify shop configurations, each with independent pricing, inventory locations, and customer mapping. Handy if you're managing stock across multiple channels with different fulfilment rules.

Method 2: Third-party connector / iPaaS platform

Sometimes the native connector doesn't cut it. Maybe you're on Business Central on-premises (the native connector is SaaS-only — more on that below). Maybe you need to sync custom metafields in both directions, or you're feeding data into additional platforms at the same time. That's where third-party integration platforms — broadly called iPaaS (Integration Platform as a Service) — come in. They sit between Shopify and Business Central and handle the translation.

The specific tool you pick matters less than getting the data mapping right. The setup process is broadly the same across platforms.

1. Choose a connector platform that explicitly lists both Shopify and Dynamics 365 Business Central as supported endpoints. Check that it supports your Business Central version (online vs. on-premises) before committing — this trips people up. Paid tiers are typically required for Business Central connectivity.
2. Create a Shopify private app or custom app in your Shopify admin under Apps > App and sales channel settings > Develop apps. Generate API credentials (API key and secret). Note: Shopify now requires custom apps rather than private apps for most API access — follow the in-platform prompts.
3. Create a Business Central API integration. In BC, register the iPaaS tool as an OAuth application or generate API credentials via Azure Active Directory App Registrations if your BC environment uses Azure AD authentication. Your BC partner or admin can help if this is unfamiliar territory.
4. Connect both endpoints in your iPaaS platform using the credentials from steps 2 and 3. Test the connection for each — most platforms show a green tick or equivalent confirmation.
5. Build your data flow mappings. This is where the real work happens. Map Shopify order fields to BC sales order fields, Shopify product variants to BC item variants, and so on. Pay close attention to: tax fields (Shopify stores tax inclusive/exclusive differently than BC expects), currency codes, and any custom metafields you use for product data.
6. Set trigger conditions — e.g. "when a Shopify order reaches Fulfilled status, create a posted shipment in BC" or "when BC inventory drops below zero, send an alert". Most iPaaS tools use trigger-action logic that's reasonably intuitive.
7. Run a test flow with a single order. Trace it end-to-end: Shopify order → iPaaS log → BC sales order. Check that line items, quantities, and customer details all land correctly.
8. Enable the flow for live data and monitor the iPaaS error log daily for the first week. Field mapping issues almost always surface in the first few days of live operation.

This approach pairs well with more complex operational setups — for example, if you're also automating your purchase order workflow or routing data to a separate warehouse management system. Think of the iPaaS layer as a central hub rather than a point-to-point pipe.

Method 3: Direct API (custom build)

This is the highest-effort option and, honestly, most SME brands don't need it. But if you have genuinely bespoke requirements — custom fulfilment logic, non-standard data models, or compliance-driven data handling — a direct API build gives you complete control.

1. Review the Shopify Admin API documentation at shopify.dev/docs/api/admin-rest or the GraphQL equivalent. Decide whether to use REST or GraphQL — GraphQL is where Shopify is heading, and newer endpoints (like Markets and B2B) are GraphQL-only.
2. Review the Business Central API documentation at learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference. BC exposes standard entity APIs (sales orders, items, customers) and supports custom APIs built via AL extensions if you need non-standard entities.
3. Create API credentials for both platforms as described in Method 2, steps 2–3. For BC, OAuth 2.0 via Azure AD is the standard auth flow for production integrations.
4. Design your data model before writing a line of code. Map every Shopify field you need to its BC equivalent. Decide which system is the master record for each entity type (products, customers, inventory). Document this — future-you will be grateful.
5. Build the integration layer — typically a middleware service (Node.js, Python, Azure Functions, etc.) that listens to Shopify webhooks for new events and writes to BC via API calls. Use Shopify webhooks rather than polling where possible; they're more reliable and lower latency.
6. Implement error handling and retry logic from day one. Both APIs rate-limit. Shopify's REST API allows a certain number of requests per second depending on your plan tier; BC has its own throttling. Your middleware needs to handle 429 responses gracefully.
7. Test with a staging environment — both Shopify and Business Central support sandbox/development environments. Don't test against live data.
8. Deploy and monitor. Build an alerting mechanism (email, Slack, whatever you use) for failed sync events. A silent failure in a custom integration can cause significant data drift before anyone notices.

If you're managing a sophisticated multi-channel operation — perhaps alongside a full DTC operations stack — the custom route gives you the flexibility to handle edge cases that break pre-built connectors. Just go in clear-eyed about the ongoing maintenance cost.

Common errors and how to fix them

Native connector not available — "Business Central on-premises" error

The official Microsoft Shopify Connector only works with Business Central in the cloud (SaaS). It isn't supported for on-premises or private cloud deployments. If you're on on-premises BC, your options are a third-party iPaaS connector or a custom API build. There's no workaround — it's an architectural constraint, not a configuration issue.

Custom field mapping mismatches causing data discrepancies

Shopify's metafields and Business Central's custom item attributes don't map automatically. If you use metafields for things like product certifications, material codes, or country-of-origin data, you'll need to configure that mapping explicitly — either in the native connector's metafield settings (expanded in the 2026 API update) or in your iPaaS field mapping. Audit your Shopify metafields before setup and build a mapping document. Fixing data discrepancies after the fact is significantly more painful than getting it right upfront.

Historical data not migrating automatically

This catches a lot of teams off guard. Integration connectors — native or third-party — handle ongoing data flows. They don't retroactively import historical orders, customers, or inventory movements from Shopify into Business Central. If you need historical order data in BC (for reporting, customer history, or financial reconciliation), that's a separate data migration project. Plan for it separately, and factor in data cleaning time — Shopify export formats don't map neatly to BC import templates without transformation.

Sync errors and duplicate records appearing in Business Central

Sync failures typically show up in Business Central's Job Queue Log or the Shopify connector's error log (accessible via the Shopify Shop Card). Common causes: API timeouts during high-traffic periods, conflicting edits to the same record in both systems simultaneously, or an item in Shopify that has no matching SKU in BC. Check the error log first — the messages are usually specific enough to act on. For duplicate customer records specifically, review your customer mapping settings; the native connector lets you match incoming Shopify customers to existing BC customers by email, which prevents most duplicates.

Frequently asked questions

Does Shopify integrate with Microsoft Dynamics 365?

Yes. Microsoft and Shopify partnered to build a native connector directly into Dynamics 365 Business Central. It synchronises orders, inventory, customers, and product data between the two platforms. Third-party and custom API approaches are also available for more complex requirements.

How do I sync inventory from Shopify to Dynamics 365?

Using the native connector, go to Shopify Inventory in Business Central and run Sync Inventory to Shopify for an immediate push, or configure the background job queue to run on a schedule. Business Central acts as the inventory master and pushes current stock levels to Shopify, which prevents overselling. You can map specific BC locations to specific Shopify locations for multi-warehouse setups.

What is the best app to connect Shopify and Dynamics 365 Business Central?

For most Business Central SaaS users, the Microsoft native Shopify Connector is the right starting point — it's first-party, maintained by Microsoft, and covers the majority of sync requirements. If you need more flexibility, custom field mapping, or you're on Business Central on-premises, a third-party iPaaS connector is the next step. A custom API build is only worth it for genuinely bespoke workflows.

Can I connect multiple Shopify stores to one Dynamics 365 environment?

Yes. Business Central supports multiple Shopify shop configurations in a single environment, each with its own setup for locations, pricing, and customer mapping. This is useful if you run separate regional storefronts — a UK store and an EU store, for example — and want to manage inventory and orders centrally. Each shop is configured independently via its own Shopify Shop Card in Business Central.

Which method should you use?

Start with the native connector if you're on Business Central SaaS and your data model is relatively standard — it's genuinely good, it's kept current (the 2026 Wave 1 update added real capability), and the maintenance burden is low. Move to an iPaaS connector if you're on on-premises BC, need bidirectional custom field sync, or want to route data to additional platforms without custom code. Reserve the direct API build for situations where the pre-built options have real gaps your business can't work around — and go in knowing you're taking on ongoing engineering responsibility.

Whatever you build: test with real order data before go-live, set up error alerting from day one, and plan your historical data migration separately. It's the step most teams skip and almost everyone regrets.

For broader operational context, the guides on choosing shipping software, ASN receiving workflows, and batch picking processes are worth reading once your ERP sync is stable — because fixing your data flow often exposes the next bottleneck downstream.

Last verified: May 2026

Sustainability used to be a marketing talking point. In 2026, it's an operational requirement. France's Refashion eco-modulation scheme, the incoming EU Digital Product Passport, and Extended Producer Responsibility obligations across multiple markets mean fashion brands can't just bolt a "conscious collection" onto their website and call it done. The data infrastructure has to be real.

At the same time, consumer demand for transparency has pushed brands to actually show their work — where a product was made, what it's made from, and what happens to it at end of life. That's a hard ask if your supply chain visibility stops at your tier-one manufacturer. Building a stack that handles all of this without collapsing under its own complexity is the actual challenge. If you're also selling on multiple channels, keeping inventory accurate across all of them adds another layer — and that's where tools like Ceendesis become relevant alongside the sustainability-specific tools in this stack.

This article covers the full sustainable fashion operations stack — from fibre-to-retail traceability through to the box your product ships in. It's built for brands at roughly the £2m–£20m revenue stage: past the spreadsheet phase, not yet at the point where enterprise procurement runs every software decision. If you're also thinking about broader DTC operations, our 7-figure DTC operations stack guide covers the commercial side in more depth.

Supply chain traceability

You can't report what you can't see. Supply chain traceability software maps your supplier network — tier one through tier four — and tracks materials as they move through it. This layer feeds your Digital Product Passport, your Refashion compliance data, and ultimately your green claims. Without it, everything downstream is guesswork. For context on how EPR obligations fit into this picture, our global EPR requirements overview is a useful starting point.

TrusTrace

TrusTrace is a supply chain traceability and compliance platform built specifically for fashion, footwear, and textile brands. It maps your supplier network, tracks materials and products through that network, and layers compliance management and forced labour risk tools on top.

Strengths

• AI-powered risk management that flags supply chain vulnerabilities before they become compliance failures
• Open API integrations with platforms like Higg, Open Apparel Registry, and circular.fashion — so it fits into a broader compliance ecosystem rather than demanding you rip out existing tools
• Dedicated forced labour prevention module, increasingly important as supply chain due diligence legislation expands across the EU and UK

Best fit

A strong choice for mid-to-enterprise fashion brands that need end-to-end supply chain visibility and have multiple compliance obligations to manage at once. TrusTrace does not publish pricing; you'll need to book a demo to get numbers.

TextileGenesis

TextileGenesis takes a different angle. It tracks materials from fibre to retail using its proprietary Fibrecoin™ token technology, creating an immutable chain of custody that's particularly useful for certified sustainable materials like organic cotton, recycled polyester, or responsibly sourced cashmere.

Strengths

• Integration with over 90% of major sustainable material certification standards — including Better Cotton, OEKO-TEX®, FSC®, and the Good Cashmere Standard — so certified claims are verifiable, not just asserted
• Supply chain mapping and discovery module that gives brands a visual picture of their full supplier network
• Native integration with EON for Digital Product Passports, which matters given the DPP timeline for textiles

Best fit

Best suited to brands selling certified sustainable materials who need that certification chain to be auditable and consumer-facing. For full-scale rollouts, the API is the preferred method, but customised API processes have historically required significant resource investment from both the brand and TextileGenesis.

ESG & sustainability platforms

Carbon accounting tells you your footprint. An ESG platform tells the whole story — across governance, reporting frameworks, Digital Product Passport obligations, and lifecycle assessment. For fashion brands with CSRD exposure or investors asking sustainability questions, this layer translates operational data into structured disclosures.

GreenStitch

GreenStitch is a textile-specific ESG and sustainability platform that handles carbon accounting, Digital Product Passports, lifecycle assessment, and structured ESG reporting under GRI, ISSB, CDP, TCFD, CSRD, and BRSR frameworks.

Strengths

• Product lifecycle assessment across 16 PEF (Product Environmental Footprint) categories — unusually granular for a mid-market tool
• Digital Product Passport functionality aligned with EU circularity mandates, with built-in auditability — important as DPP implementation rolls out staggered across product categories
• Free tier available, so brands can start measuring before committing to enterprise tooling

Best fit

A strong choice for fashion and textile companies that want a single platform for both regulatory compliance and investor-grade ESG disclosures. It's highly specialised for fashion and textiles — if you run a mixed-category business, a more general ESG tool may cover more ground.

Carbon accounting

Scope 3 emissions — the upstream and downstream carbon in your supply chain — are where most of a fashion brand's footprint lives. Generic carbon accounting tools don't understand the nuances of textile manufacturing; the tools in this category are built around how the industry actually works. France's Refashion scheme uses eco-modulation that rewards lower-impact products, which means your carbon data directly affects your Refashion fee calculations.

Carbonfact

Carbonfact is a carbon measurement and reporting platform built exclusively for apparel, footwear, textile, leather, and luxury. It ingests data from PLM systems, ERPs, and even Excel files, runs product-level lifecycle assessments, and produces GHG Protocol-compliant reports across Scope 1, 2, and 3.

Strengths

• Product-level LCA engine — not just brand-level carbon totals, but per-SKU footprint data that can feed Digital Product Passports and eco-modulation calculations
• Scenario modelling and eco-design tools that let you simulate the carbon impact of material swaps before you commit to them
• Integrations with major PLM systems (Centric, Lectra, PTC) and ERPs (SAP, Oracle, Microsoft Dynamics), plus data warehouses like Snowflake and BigQuery

Best fit

Purpose-built for brands that need granular product-level carbon data for regulatory filings and eco-design decisions. It's tailored exclusively for apparel and footwear — if your business spans categories outside fashion, you'll need a second tool for the rest.

Watershed

Watershed is an enterprise carbon management platform covering Scope 1–3 measurement, CSRD and TCFD disclosure automation, and decarbonisation pathway analysis. It's used across industries, not just fashion.

Strengths

• Comprehensive Scope 1–3 measurement with AI-powered data collection and standardisation — useful when your supply chain spans dozens of suppliers with inconsistent data quality
• Automated ESG reporting and disclosure aligned to CSRD and TCFD, cutting the manual burden of annual sustainability reports
• Strong decarbonisation forecasting tools for brands with formal net-zero commitments

Best fit

Best suited to larger brands with formal net-zero targets, institutional investors, or CSRD reporting obligations. Pricing is custom-quoted and enterprise-tier; growing fashion brands at the SME end will likely find Carbonfact or GreenStitch more proportionate.

3D design & sampling

Physical sampling is one of the most wasteful parts of fashion product development — and one of the most overlooked. A small brand's development cycle might involve four or five rounds of physical samples per style, with real material and shipping waste at each iteration. 3D design tools compress that process considerably. They won't eliminate physical sampling entirely for most brands, but cutting three rounds down to one is a realistic target. And that has a direct carbon impact, not just a cost one.

CLO 3D

CLO 3D is a 3D garment simulation and design platform that lets fashion designers build, visualise, and iterate on digital garments in a realistic virtual environment — including fabric behaviour, drape, and fit.

Strengths

• Realistic fabric simulation using the CLO zFab Kit for material digitisation, so digital samples behave the way the actual fabric would
• AI-powered design capabilities via CLO AI Studio, accelerating the ideation phase
• Free tier available, along with integrations with Adobe Substance 3D and Epic Games for brands that want to push assets into marketing or virtual retail contexts

Best fit

Well-suited to fashion designers and apparel companies looking to cut physical sample rounds and speed up development timelines. Pattern precision issues do persist — distorted armholes and manual grading limitations for custom avatars often mean relying on separate software for accuracy.

Browzwear

Browzwear is a 3D fashion design platform built around its VStitcher tool for AI-powered garment design and fit validation, alongside Stylezone for collaborative review and a Fabric Analyzer for physical fabric digitisation.

Strengths

• Open platform with APIs for integration with PLM and ERP systems, so it embeds into an existing product development workflow rather than running in parallel
• Collaborative 3D review via Stylezone, which cuts the back-and-forth between designers, developers, and buyers that typically drives extra sample rounds
• Free tier available for teams that want to test before committing

Best fit

A strong fit for apparel brands and manufacturers looking to digitally transform their product development workflow end-to-end. The software has a real learning curve — factor in training time when planning rollout.

Circular commerce platforms

The recommerce market is growing at roughly 9.5% annually, and branded resale has shifted from a sustainability story to a genuine revenue channel. This layer of the stack handles the operational complexity of returns, trade-ins, condition grading, and resale — either through a full recommerce operating system or a peer-to-peer marketplace. For brands also managing returns on Shopify, our guide to the best Shopify returns apps covers the commercial returns side in parallel.

Trove

Trove is a white-label recommerce operating system. It handles trade-in programmes, reverse logistics, AI-powered condition grading, and resale channel management for retail brands that want branded resale rather than sending customers to third-party marketplaces.

Strengths

• AI-powered inventory processing using computer vision, automated condition grading, and predictive analytics — cutting the manual labour cost of handling returned and traded-in items
• ML-powered active pricing models for resale items, so you're not leaving money on the table with static price points
• Integrations with Shopify, Salesforce Commerce Cloud, BigCommerce, and existing OMS, WMS, ERP, and CRM platforms

Best fit

Best suited to retail brands at meaningful scale that want to run a profitable branded resale programme rather than a basic returns process. Available in North America, UK, and EU.

Depop

Depop is a social peer-to-peer marketplace for buying and selling secondhand, vintage, and trend-driven fashion — with a free tier and a community-first model that skews younger than most resale platforms.

Strengths

• AI-powered listing generation from images, with in-app photo editing tools including background removal — lowering the barrier for small sellers to list consistently
• Free to list and sell in the UK and US, with prepaid shipping labels included, so the acquisition cost for the channel is essentially zero for qualifying sellers
• Shop stats dashboard for tracking performance across listings, useful for brands testing secondhand as a channel before investing in a full recommerce platform like Trove

Best fit

A natural starting point for small brands or individuals wanting to test secondhand commerce with minimal setup. Sellers outside the UK or US pay a Depop selling fee — factor that into your margin calculations if you're operating from other markets.

Sustainable packaging

Sustainable packaging isn't just an ethical choice anymore — it's an EPR compliance consideration. Whether you're registered under the UK packaging EPR scheme (large producers handle over 50 tonnes annually with turnover above £2 million), reporting under Germany's VerpackG, or working through France's CITEO obligations, what you put your products in now carries a regulatory cost. Our multi-country EPR packaging compliance guide covers the reporting mechanics in detail, and our EPR packaging obligations calculator helps you work out what you actually owe.

EcoEnclose

EcoEnclose is a sustainable packaging supplier offering recycled, recyclable, and compostable solutions across mailers, boxes, tissue, and void fill — with custom branding using eco-friendly inks including their proprietary Algae Ink™.

Strengths

• Wide materials range across 100% recycled, recyclable, and compostable options — covering most fashion e-commerce packaging scenarios from polybags to shipper boxes
• Custom branding with Algae Ink™ and other eco-friendly inks, so sustainable packaging doesn't mean plain brown boxes
• Climate Neutral Certified, with a free sample pack available to test before ordering at volume

Best fit

A solid first choice for e-commerce fashion brands in North America looking to clean up their outbound packaging without a complex procurement process. Customisable packaging dimensions may have varying minimum order quantities by SKU — check specific MOQs before locking in a design.

Bolt Boxes

Bolt Boxes is a UK-based custom packaging manufacturer offering branded corrugated boxes made from 60–95% post-consumer waste, with digital, litho, and flexo printing across a range of box styles.

Strengths

• Multiple box styles — RSCs, mailer boxes, tray and cover, half slotted containers — plus three material strength grades (Standard, Strong, Extra Strong) to match different product weights and transit requirements
• In-house design, printing, manufacturing, and delivery, which keeps lead times fast compared to suppliers that outsource any part of that chain
• 100% recyclable kraft board from high post-consumer waste content, making the sustainability credentials straightforward to report against EPR packaging schemes

Best fit

Well-suited to UK and EU-based fashion brands wanting custom branded packaging with genuine sustainable credentials. For projects with printing, all spot colours are converted to 4CP for digital production — worth knowing if your brand uses specific Pantone colours.

Inventory & compliance operations

Running a sustainable fashion brand across multiple sales channels creates real operational complexity. Inventory sync, marketplace payout reconciliation, and EPR compliance reporting all need to work together. This is where an operations platform earns its place in the stack.

Ceendesis

Ceendesis is a multi-channel operations platform that combines inventory management, EPR compliance (including Textile Compliance for Refashion, Netherlands UPV, REACH, and the EU Digital Product Passport), and marketplace-to-accounting reconciliation in a single platform.

Strengths

• Combines multi-channel inventory, EPR compliance, and marketplace-to-accounting sync in one place — cutting the number of point solutions needed for brands selling across Shopify, Amazon, eBay, Walmart, and TikTok Shop
• Native Xero and QuickBooks reconciliation for marketplace payouts, which matters when your accountant needs clean numbers from five different channels
• Built for brands that need to manage textile EPR obligations (Refashion, Netherlands UPV, EU labelling, REACH, DPP, Green Claims) alongside their commercial operations, without running two separate systems

Best fit

Built for brands on 2+ marketplaces — overkill for single-channel Shopify-only stores. If you're selling into France and need to understand your Refashion obligations, our Refashion eco-modulation guide explains how the fee structure works.

The stack at a glance

Frequently asked questions

What software do sustainable fashion brands use?

There's no single answer. Sustainable fashion operations typically span several categories of tool. For supply chain visibility, brands use platforms like TrusTrace or TextileGenesis. Carbon footprinting is handled by tools like Carbonfact (fashion-specific) or Watershed (enterprise-grade). ESG reporting and Digital Product Passport preparation sits in platforms like GreenStitch. On the commercial side, 3D design tools like CLO 3D and Browzwear cut physical sample waste, while circular commerce platforms like Trove enable branded resale. Multi-channel brands also need inventory management and compliance automation — Ceendesis covers inventory, EPR textile compliance, and accounting sync together. The right combination depends on your scale, your markets, and which regulations you're currently exposed to.

How do you build a transparent supply chain for apparel?

Start by mapping what you actually know versus what you're assuming. Most brands have good visibility to tier one (cut-and-sew) but limited visibility to tier two (fabric mills) and almost none beyond that. Tools like TrusTrace and TextileGenesis provide the structure to request, collect, and verify data from each supplier tier. The practical starting point is usually a supplier onboarding questionnaire — then software to systematise data collection rather than manage it in spreadsheets. Material certification standards (Better Cotton, OEKO-TEX®, GRS) give you third-party verification at specific points in the chain. And if you're selling into the EU, start preparing for the Digital Product Passport requirements now — the textile delegated act is expected between late 2026 and early 2027, with an 18-month compliance window after adoption.

What is a circular fashion business model?

A circular fashion business model keeps products and materials in use for as long as possible, rather than following the linear take-make-dispose pattern. In practice, that means designing for durability and repairability, running trade-in or resale programmes (like a Trove-powered branded resale channel), offering repair services, and ensuring end-of-life recyclability. It can also mean using recycled or certified sustainable inputs at the production stage. The commercial case is increasingly strong — the recommerce market is growing at around 9.5% annually, and brands running resale programmes generate revenue from stock that would otherwise generate a cost (returns, waste). France's AGEC Law and the EU's Ecodesign for Sustainable Products Regulation (ESPR) are also pushing circularity from a regulatory direction, so it's not just a positioning choice.

How do I prepare for the EU Digital Product Passport?

The EU Digital Product Passport is a digital record that must travel with a product across its lifecycle, covering materials, sustainability attributes, repairability, and recycling instructions. For textiles, the DPP is expected to become mandatory from approximately mid-2028 — the textile-specific delegated act is expected between late 2026 and early 2027, after which there's an 18-month window. The preparation steps now are: build your supply chain data infrastructure (TrusTrace or TextileGenesis are both relevant here), start collecting product-level carbon and material data (Carbonfact or GreenStitch), and make sure your product data is structured and exportable rather than locked in PDFs and email threads. If you also need to understand the compliance tracking side, Ceendesis Textile Compliance covers DPP obligations alongside Refashion, REACH, Netherlands UPV, and EU labelling requirements. Our Refashion eco-modulation guide is a good companion read.

What's essential now vs. what can wait

If you're under £2m revenue and selling primarily on Shopify, the full stack above is overkill. Start with one 3D design tool to cut sample rounds (CLO 3D has a free tier), sort your packaging (EcoEnclose or Bolt Boxes), and use GreenStitch's free tier to start measuring your footprint. That's a meaningful stack without significant spend.

At the £2m–£10m stage, add a traceability layer. If your product uses certified sustainable materials, TextileGenesis is the more targeted choice. If you need broader supply chain due diligence coverage across multiple supplier tiers, TrusTrace is worth the investment. And if you're selling into France, you need to be registered with Refashion — our eco-modulation guide explains how those fees are calculated.

Multi-channel brands above £5m selling on Amazon and Shopify simultaneously and handling EPR compliance in multiple markets should add Ceendesis for the operational layer — inventory sync, EPR compliance automation, and accounting reconciliation together. And if branded resale is a real conversation at your scale, Trove is the platform that makes it commercially viable rather than operationally painful.

Watershed and Carbonfact are enterprise considerations — the right tools, but the investment is proportionate to scale. For most growing brands, GreenStitch covers enough of the carbon and ESG reporting ground until you have formal net-zero targets or CSRD obligations in play. Build the data infrastructure now. The regulatory window for DPP preparation is shorter than it looks.

Screenshots are from each tool's public pricing or features page, captured May 2026. We are not affiliated with any third-party tool listed unless explicitly noted.