DTC and Retail Integrations · Updated September 2026
DTC and retail integrations for apparel ERP: every consumer channel, one stock record, one order queue
A consumer order can come from your own web store or register, from a marketplace where you are the seller of record, or from a retailer that sold the item on its site and wants you to ship it. AIMS360 connects to all three kinds: Shopify and Shopify POS natively, the sales channels and marketplaces that sell through Shopify, Amazon across its programs, Mirakl powered retailer marketplaces and Farfetch per program, and retailer dropship over native EDI. Every one of them draws on the same open to sell figure and lands in the same customer orders module beside your wholesale and EDI orders.
AIMS360 connects to consumer channels in three ways. Your own channels: Shopify and Shopify Plus web stores and Shopify POS registers, natively, plus any Shopify sales channel such as TikTok Shop or Facebook and Instagram Shops. Marketplaces where you are the seller: Amazon Seller Central FBM through Shopify or the Amazon FBM automation, Amazon FBA by API, Walmart Marketplace, Target Plus and eBay through Shopify's marketplace app, and Mirakl powered retailer marketplaces and Farfetch configured per program. Retailer dropship: Dsco, Rithum, Walmart drop ship vendor and Wayfair over native EDI. Styles and open to sell go out per location, orders come in paid, pick tickets are created automatically, the order ships from a warehouse, a store or a 3PL, and fulfillment goes back to the channel.
Which DTC and retail channels integrate with AIMS360?
The table lists what is documented and live. How a channel connects decides how fresh the availability is and what comes back, so the mechanism sits beside the name. Channels that are not on this list are not native connections; the last FAQ below covers the routes for those.
| Channel | What it is | How it connects to AIMS360 | Orders arrive |
|---|---|---|---|
| Shopify and Shopify Plus | Your web store. The native cart connection, listed on the Shopify App Store since January 2016. | Styles, colors, sizes and images exported from the style master; open to sell pushed per Shopify location in real time; orders imported paid and unfulfilled with the payment as a pre-payment; fulfillment and tracking sent back. More than one store per company. | Automatically, on the import automation. |
| Shopify POS | Your stores. Each register location is its own AIMS360 warehouse and customer account. | Register sales import as paid orders and are picked and invoiced automatically; web orders can be picked up in store or shipped from the store; returns and exchanges at the register post as return authorizations and credits. | Automatically, as register sales are made. |
| TikTok Shop, Facebook and Instagram Shops | Social selling channels connected to your Shopify store. | Orders appear in Shopify like any other order and import on the same automation; a tag routes each channel to its own customer account while the source stays Shopify. Facebook and Instagram orders arrive authorized and on hold, so they import once they are paid. | With the Shopify import, once paid and unfulfilled. |
| Amazon Seller Central (FBM) | Amazon's third party marketplace with you as seller of record, shipping the orders yourself. | Through the Shopify integration with an Amazon flag so those orders can be scheduled and reviewed separately, or through the Amazon FBM automation. AIMS360 is a listed app in the Amazon Selling Partner Appstore. | On a timed automation, tagged with the Amazon source. |
| Amazon FBA | Your stock in Amazon's fulfillment centers, Amazon picks, packs and ships. | A direct sales channel by API. Shipped FBA orders are pulled back into AIMS360 as orders, pick tickets and invoices, so units Amazon shipped leave your books and the stock at Amazon stays your asset until it sells. | Automatically, as Amazon ships them. |
| Walmart Marketplace, Target Plus, eBay | Marketplaces where you are the seller of record. | Through Shopify's marketplace app, which carries Shopify's own fee: marketplace orders flow into Shopify, then into AIMS360 on the Shopify import, and inventory stays in step through the same Shopify sync. | With the Shopify import. |
| Mirakl retailer marketplaces | The marketplaces retailers such as Macy's, Bloomingdale's, Nordstrom and Ulta run on their own sites; you list, price, hold the stock and ship, the retailer takes a commission. | Configured per retailer program during implementation, because each runs its own catalog spec and service levels. Marketplace orders join the same queue as bulk EDI, dropship and your own ecommerce. | Per program, into one queue. |
| Farfetch | The luxury marketplace: you hold the stock and fulfill single consumer orders in luxury grade packaging. | Not an X12 cycle. A catalog with a UPC per size, availability with commitments netted out, consumer orders into one queue, shipments and returns back, configured to your program. | Per program, one at a time as they sell. |
| Dsco and Rithum | The dropship networks behind many department store and specialty dropship programs: the retailer sells, you ship to the shopper. | Native EDI with years of live programs behind it: 850 in, 855 back, 856 with GS1-128 carton labels, 810 invoice and the 846 inventory feed the retailer's site sells against. | As 850 purchase orders, one shopper each. |
| Walmart and Walmart Canada | Four Walmart programs: bulk supplier, drop ship vendor, Marketplace and WFS; Walmart Canada is its own vendor agreement. | Bulk and drop ship vendor orders on one native EDI connection with the document set, packaging and label rules applied per program; Marketplace through Shopify's marketplace app; Walmart Canada with bilingual labeling and Canadian dollar invoicing. | As 850s, or through Shopify for Marketplace. |
| Wayfair | Dropship and small parcel supplier programs for home goods. | Native EDI: 850 and 860 in; 855, 856 with matching carton labels, 810 and the 846 inventory feed Wayfair requires several times a day out. Mapping, testing and certification handled by the AIMS360 team. | As 850 purchase orders. |
What every one of these has in common
The consumer is a ship to on an order, not a customer account. Each store, channel or marketplace imports against one customer account you create for it, the shopper rides on the order as bill to and ship to, and the payment already taken arrives as a pre-payment the invoice consumes. That is what keeps ten thousand shoppers out of the customer list and still puts every one of them on an order, an invoice and a label. The B2C direct to consumer page is the record level view.
A cart that is not Shopify?
Shopify is the native cart connection and the reason most AIMS360 brands run their web store on it. Another cart connects through a connector partner scoped per program, the AIMS360 Open API, or the order import for a cart that exports orders to a spreadsheet. None of those is a marketplace toggle; ask about the cart during scoping.
Three kinds of consumer order, and why the ERP has to know which is which
They look alike on a packing bench, one or two units in a parcel to somebody's door. They are not alike in who sold the item, whose money it is and whose rules the parcel ships under.
| Your own channels | Marketplaces | Retailer dropship | |
|---|---|---|---|
| Examples | Shopify web store, Shopify POS, TikTok Shop, Facebook and Instagram Shops | Amazon Seller Central, Walmart Marketplace, Target Plus, eBay, Mirakl powered retailer marketplaces, Farfetch | Dsco and Rithum programs, Walmart drop ship vendor, Wayfair dropship, and the dropship programs of your EDI retailers |
| Who sells | You, on your own storefront or register | You, as seller of record on someone else's storefront | The retailer, on its own site, at its own price |
| Who ships | You, from a warehouse, a store or a 3PL | You, or Amazon on FBA | You, on the retailer's carrier account and packaging rules |
| How the order arrives | Paid and unfulfilled in Shopify, imported with the pre-payment | Through Shopify's marketplace app, the Amazon connections, or per program | An 850 purchase order with the shopper's address in the ship to |
| The money | The cart takes the card; the invoice consumes the pre-payment | The marketplace pays you net of its referral fee or commission | You invoice the retailer with an 810 off what shipped; the retailer pays on terms |
| Compliance | Your own rules | The marketplace's listing, service and returns standards | Routing guides, packing slips, carton labels, an 856 before the freight lands, chargebacks when missed |
| What the channel sells against | Open to sell pushed to its location | Availability published from the same record | Your 846 inventory feed, which is why it matters more here than anywhere |
AIMS360 keeps all three in one order queue on one stock record and applies the compliance work only where it belongs. The dropship side is covered on the EDI dropship page; how each of these ships is on multi-channel distribution.
How a consumer order runs through AIMS360, cart to books
The same six steps run whether the order came from your web store, a register, a marketplace or a dropship retailer. Only the way it arrives in step three and the way the channel is told in step six change.
- Publish the line once. Styles with colors, sizes and images are exported from the AIMS360 style master to each Shopify store and POS location, or mapped to listings that already exist. A style's scope decides whether it is available online, at the register or both.
- Publish availability per location. An OTS template calculates open to sell for each location from stock, allocations and, if you choose, work in process due within a window. Wholesale, EDI and marketplace commitments come out first, and the result is pushed to the matching Shopify location in real time. Negative availability is sent as zero.
- The shopper pays. The cart takes the card and the order is paid and, with the checkout set never to auto fulfill, unfulfilled, which is the state AIMS360 imports. A marketplace order arrives through Shopify's marketplace app or the Amazon connection; a dropship retailer sends an 850.
- The order imports. AIMS360 creates the order on the customer account for that channel: shopper as bill to and ship to, pre-payment attached, discount as an amount, shipping method mapped to a ship via, warehouse from the location. An order that fails validation is held with the reason and re-run, and an order still authorized rather than paid is retried until it catches up.
- Pick, ship and confirm. A pick ticket is created immediately and exported to your warehouse system, a store or a 3PL; intelligent allocation can reserve the units by rule first. The shipment is confirmed, the pick ticket carries tracking, cartons, weight and freight, and the invoice consumes the pre-payment. The unattended version of this chain is DTC and 3PL fulfillment automation.
- Tell the channel. The order is fulfilled in Shopify with the tracking number, which triggers the shopper's notification; a pickup order is marked picked up instead; a dropship retailer gets the 856 and the 810; Amazon FBA orders were already shipped by Amazon and are recorded as such. Every step is a logged workflow you can read and re-run.
The design decision underneath all of it: availability is calculated in the ERP and pushed to the channel, never the other way round. A cart can only see its own orders; it cannot see the wholesale order a rep wrote this morning, the EDI purchase order that landed at noon or the units a 3PL already picked. AIMS360 can, which is why the number the storefront shows is the number the warehouse can ship.
What moves between AIMS360 and each channel, and in which direction?
Each row is what the live connection is documented to do. Where a cell says per program, your implementation manager confirms scope for that retailer or marketplace.
| Channel | Line out | Availability out | Orders in | Back to the channel | Returns |
|---|---|---|---|---|---|
| Shopify web store | Yes, styles, colors, sizes, images | Yes, per location, real time | Yes, paid and unfulfilled | Yes, fulfillment with tracking | Yes, via Loop, Redo or an RMA |
| Shopify POS | Yes, with global scope | Yes, the store's own warehouse | Yes, register sales | Yes, marked fulfilled, no email | Yes, at the register as RMA and credit |
| Shopify sales channels (TikTok, Facebook, Instagram) | Through the Shopify listing | Yes, through the Shopify sync | Yes, once paid; routed by tag | Yes, through Shopify | Through Shopify |
| Amazon Seller Central FBM | Listings managed in Seller Central | Yes, through the Shopify sync | Yes, flagged as Amazon | Yes, tracking written back | Per Amazon policy, recorded in AIMS360 |
| Amazon FBA | No | Stock at Amazon stays your asset | Yes, shipped orders pulled back | No, Amazon already shipped | From Amazon reports, not the connection |
| Marketplaces through Shopify's app | Through the Shopify listing | Yes, through the Shopify sync | Yes, with the Shopify import | Yes, through Shopify | Through the marketplace |
| Mirakl retailer marketplaces | Per program, catalog spec per retailer | Yes, per program | Yes, into one queue | Per program | Per program |
| Farfetch | Yes, catalog with a UPC per size | Yes, commitments netted | Yes, one at a time | Yes, shipments | Yes, returns flow back |
| Dsco, Rithum, Walmart DSV, Wayfair | Item setup in the retailer portal | Yes, 846 inventory feed | Yes, 850 purchase orders | Yes, 855, 856, 810, 997 | Manual; retailer handles the shopper |
Shopify as the switchboard: sales channels, tags and marketplaces
A lot of what looks like a long list of integrations is one connection. Anything that puts an order into Shopify with the right style, color and size on it imports into AIMS360 on the same automation, whether it came from the storefront, a social channel or a marketplace. Three things make that workable rather than messy.
Tags route channels to accounts
By default every Shopify order imports against the store's customer account and the channel breakout lives in Shopify. Map a tag, TikTok for example, to a customer account you created for that channel, and those orders import against it instead, so views, batch picking and reports can filter one channel alone. The order source still reads Shopify.
Amazon FBM gets its own flag
Amazon orders arriving through Shopify are flagged as Amazon inside AIMS360, so they can be scheduled, reviewed and routed separately from your other Shopify traffic even though they import under the same account. FBA is a separate connection because Amazon does the shipping.
Marketplaces through Shopify's app
Amazon FBM, Target Plus, Walmart Marketplace and eBay connect to Shopify through Shopify's marketplace app, available on every Shopify plan with Shopify's own monthly fee. Orders flow into Shopify and then into AIMS360; inventory stays in step through the same sync. Add or drop a marketplace without touching the ERP connection.
Paid and unfulfilled, or it waits
AIMS360 imports orders that are paid and unfulfilled. Facebook and Instagram orders arrive authorized and on hold, so they fail the first import and succeed once the payment settles, sometimes after a re-run of the failed workflow. Gift card only orders, which Shopify marks fulfilled, do not import.
The Shopify page covers the connection itself, locations, product shape and setup; the Shopify POS page covers the registers.
What the DTC and retail integrations do not do
Stated plainly, because these are the questions that surface in month two.
| Constraint | Detail |
|---|---|
| Shopify is the native cart | WooCommerce, BigCommerce, Magento and other carts are not native connections. They can be reached through a connector partner, the Open API or the order import, scoped per program; the Shopify connection itself works on every Shopify plan. |
| The card lives in the cart | AIMS360 records the pre-payment, the invoice, the credit and the refund adjustment; the charge and the refund themselves are done in the cart or marketplace. A refund is two steps: one there, one on the account. |
| One line, one location, one product shape | Shopify does not split a single order line across locations. The choice between one product per style with variants and one product per color is made when the store is connected. A single store cannot carry retail and wholesale prices from AIMS360 at the same time. |
| Social and gift card orders wait | Facebook and Instagram orders import once paid, which can take up to a day. Orders paid only by gift card, which Shopify marks fulfilled, do not import at all. |
| Channel reporting needs tags | Without a tag mapped to its own account, a sales channel's orders import against the store account and the breakout has to be run in Shopify. |
| FBA returns and marketplace disputes are theirs | FBA returns are processed from Amazon's reports rather than through the connection; marketplace disputes, chargebacks and fee changes are set by the marketplace. Vendor Central chargebacks are covered on the Vendor Central page. |
| Not self serve | The Shopify app installs from the App Store, but every connection is activated and mapped with the AIMS360 team, and the customer account each channel imports against needs terms, ship via and a rep before orders import cleanly. Marketplace and dropship programs are configured per retailer during implementation. |

DTC and retail integration questions, answered
Which ecommerce platforms and marketplaces integrate with AIMS360?
Shopify and Shopify Plus are the native cart connection, with Shopify POS for stores. Anything that sells through a Shopify sales channel imports the same way, which covers TikTok Shop, Facebook and Instagram Shops, and Amazon FBM, Target Plus, Walmart Marketplace and eBay through Shopify's marketplace app. Amazon has its own connections: Seller Central FBM orders through Shopify or the Amazon FBM automation, FBA as a direct sales channel by API, and Vendor Central over EDI. Retailer marketplaces run on Mirakl and Farfetch connect per program, and retailer dropship through Dsco, Rithum, Walmart and Wayfair runs over native EDI. All of them land in the same customer orders module.
What order management system do DTC brands use, and is AIMS360 one?
Most DTC brands start with the order screen inside their cart, then add a separate order management system once wholesale, stores or marketplaces appear and the cart can no longer see what the other channels have committed. AIMS360 is that order management system, built into a consumer brands ERP: every channel's orders sit in one queue, intelligent allocation reserves units across them by rule, and the same record runs the warehouse, EDI, invoicing and accounting. The omnichannel orders hub covers the order management side; this page covers which consumer channels connect and how.
Does AIMS360 integrate with TikTok Shop, Instagram and Facebook Shops?
Through Shopify, yes. Orders from a Shopify sales channel appear in Shopify like any other order and import into AIMS360 on the same automation; a tag can route each channel to its own customer account so it reports separately, while the order source stays Shopify. One caveat on Facebook and Instagram: their orders arrive authorized and on hold, and AIMS360 imports only orders that are paid and unfulfilled, so they import once the payment status changes, which can take up to a day, sometimes after re-running the failed workflow. The Shopify page covers the connection.
How do Amazon orders get into AIMS360?
It depends on the program, because Amazon is three relationships. Seller Central orders you ship yourself (FBM) arrive through the Shopify integration with an Amazon flag so they can be scheduled and reviewed separately, or through the Amazon FBM automation. FBA orders come back through the FBA API connection as shipped orders, so units Amazon shipped still leave your books. Vendor Central, the wholesale program, runs over native EDI with the 850, 855, 856 and 810. AIMS360 is a listed app in the Amazon Selling Partner Appstore. The Amazon hub separates the three, and Seller Central, FBA and Vendor Central each have a page.
Does AIMS360 work with WooCommerce, BigCommerce or Magento?
Not as native connections. Shopify is the cart AIMS360 connects to directly, and the depth of that connection, per location availability, paid and unfulfilled import, fulfillment back, POS, sales channels, is why most AIMS360 brands run their web store on it. A brand on another cart has three routes: a connector partner scoped per program, the AIMS360 Open API, which exposes styles, inventory, customers and orders, or the order import for a cart that exports orders to a spreadsheet. Ask about the cart during scoping rather than assuming a listing on a partner directory means a live connector.
How does inventory stay accurate between the web store, the stores and the warehouse?
One stock record, calculated in AIMS360 and pushed out. An OTS template decides what counts as open to sell for each location, stock, allocations and optionally work in process within a window, and that figure is published to the matching Shopify location: the warehouse to the web store, each store's warehouse to its POS location, a 3PL to its location. Wholesale, EDI and marketplace commitments come out of the pool before the storefront sees a quantity, and availability recalculates on every allocation, receipt, return and shipment. Negative open to sell is sent as zero so the cart never sells units you do not have. Multi-warehouse is what makes the per location part work.
What is the difference between a marketplace order and a retailer dropship order?
Who sells and who ships. On a marketplace such as Amazon Seller Central, a Mirakl powered retailer marketplace or Farfetch, you are the seller of record: you list, you set the price, you hold the stock, you ship, and the marketplace takes a fee. On retailer dropship, the retailer sells the item on its own site and sends you the order as an 850 purchase order with the shopper's address in the ship to, you ship on the retailer's account under its packaging and label rules, and you send back the 856 with tracking and the 810 invoice; the retailer never holds the goods, so your 846 inventory feed is what its site is selling. AIMS360 runs both from the same record; the compliance work applies to the dropship side. The EDI dropship page has the detail.
Can a web order ship from a store, or be picked up in store?
Yes, when a store is a Shopify POS location tied to its own AIMS360 warehouse. A store allowed to fulfill web orders can offer local pickup at checkout, in which case the order arrives with no ship to address and a pickup ship via, still gets a pick ticket and an invoice, and is marked picked up from Shopify. A store that holds the units can also have the web order routed to it and ship it, with the fulfillment going back to Shopify with tracking. The B2C retail store page walks through both, and returns and exchanges taken at the register post as return authorizations and credits.
How are returns handled for DTC orders?
Three ways. A connected returns app such as Loop or Redo sends the return into AIMS360, which creates the return authorization, receives the unit and issues the credit memo, with the refund issued in the cart. A return or exchange taken at a Shopify POS register does the same for web orders carried into a store. Anything else is entered as a return authorization against the original invoice. FBA returns are processed from Amazon's reports rather than through the connection. The returns management hub covers the apps.
Does AIMS360 connect to Walmart, Wayfair, Macy's marketplace or Farfetch?
Yes, each in the way that program works. Walmart runs four programs on one native EDI connection: bulk supplier orders, drop ship vendor orders, Walmart Marketplace (through Shopify's marketplace app) and WFS; Walmart Canada is a separate vendor agreement with bilingual labeling and Canadian dollar invoicing. Wayfair dropship and SPO run over native EDI with the 846 inventory feed Wayfair requires several times a day. Macy's, Bloomingdale's, Nordstrom, Ulta and others run their marketplaces on Mirakl, and each retailer's program is configured during implementation because each has its own catalog spec. Farfetch is a catalog, stock and order flow rather than an X12 cycle, configured to your program.
What happens with the payment on a consumer order?
The shopper pays in the cart. The order imports with a pre-payment for the full amount, the invoice consumes it, and the account for that channel shows the sale and the payment. A partial shipment leaves a pre-payment balance, which is released to a credit memo and cleared with a receivables adjustment when the refund is issued in the cart. AIMS360 never charges or refunds the card; that stays in the cart or the marketplace, and on a marketplace the platform pays you net of its fees. The B2C direct to consumer page follows the money through a partial shipment step by step.
Is AIMS360 an ERP for DTC brands or for wholesale brands?
Both at once, which is the point. AIMS360 is a consumer brands ERP: apparel, footwear, accessories, beauty, jewelry, home and other consumer product brands that sell through some mix of their own web store and stores, marketplaces, wholesale accounts and EDI retailers. A DTC only brand gets the Shopify connection, POS, allocation, warehouse and accounting on one record; a brand that later adds wholesale or a department store account adds the B2B platforms and EDI retailers to the same record instead of a second system. Most brands on AIMS360 run three or more channel types.
Which Shopify plan do I need for the AIMS360 connection?
Any Shopify plan, Basic through Shopify Plus. Shopify B2B, for wholesale on the storefront, is a Shopify Plus feature. Shopify's marketplace app for Amazon FBM, Target Plus, Walmart Marketplace and eBay is available on every Shopify plan and carries Shopify's own monthly fee. More than one Shopify store can connect to one AIMS360 company, each with its own exported styles and its own customer account. The Shopify page lists the setup.
Bring us a day of consumer orders
Web orders, a few register sales, an Amazon order and a dropship 850 from a department store. We will run them through in a demo and show you one queue, one stock record and the books afterward, with the cart and the retailer portal open beside it.
Related AIMS360 pages
- B2C direct to consumer is the record level view: what a web order carries and what happens to the money after a partial shipment.
- B2C retail store covers the register: walk in sales, pickup, ship from store, returns and exchanges.
- DTC and 3PL fulfillment automation is the unattended chain from cart to doorstep across the four places an order can ship from.
- Shopify and Shopify Plus and Shopify POS are the deep pages for the native connection.
- Amazon separates Vendor Central, Seller Central, FBA and FBM, with a page for each.
- EDI dropship, Dsco and Rithum cover the retailer dropship side.
- Mirakl and Farfetch cover the retailer marketplaces.
- Omnichannel orders is the features hub for every order channel, and omnichannel B2B is the wholesale side of this page.
- Shipping, 3PL and returns management are the hubs a consumer order passes through after it imports.
- Most popular apparel software integrations shows where Shopify and Amazon sit beside QuickBooks, EDI and the 3PLs.
Written by the AIMS360 team. Reviewed 15 September 2026. Integration scope reflects the AIMS360 connections as of that date and is confirmed for your program during implementation. Marketplace and platform names belong to their owners; their fees and policies are theirs and change without notice.



































