Sell to consumers through your web store, marketplaces, Amazon and stores from the same inventory, order pool and books as wholesale. Orders import paid onto one account per channel, pick automatically, ship from a warehouse, a store or a 3PL, and fulfill back to the cart with tracking.
B2C direct to consumer in AIMS360 means your web store, your marketplaces and your registers sell from the same inventory, into the same order pool and onto the same books as your wholesale accounts. A shopper's order downloads from the cart already paid, becomes an order on the store's account, picks from the warehouse that holds the units, ships from your warehouse, a store or a 3PL, invoices against the payment already taken, and fulfills back to the cart with tracking. No second system for consumer sales, and no consumer in the customer list.
B2C direct to consumer in AIMS360 is the consumer side of one order management system: orders from your Shopify web store, from marketplaces connected through it, from Amazon and from Shopify POS registers download automatically, become orders on a customer account per store or channel with the shopper as bill to and ship to, carry the payment taken in the cart as a pre-payment, pick from the warehouse tied to their location, ship from your warehouse, a store or a 3PL, invoice against the pre-payment, and fulfill back to the cart with tracking. Open to sell is pushed to the store per location so the cart sells what the warehouse can ship, and every consumer sale lands in the same cost, margin and receivables records as a wholesale invoice.
The DTC fulfillment automation page follows the order from cart to doorstep across the four places it can ship from. The Shopify page covers the connection, and the B2C retail store page covers the register. This page is about the consumer order itself: what it looks like inside a wholesale system, and what happens to the money.
| Field | What it holds |
|---|---|
| The account | A consumer is not a customer account. Every web order lands on one customer account you create for the store, and the shopper's name and address ride on the order as bill to and ship to. A second store, a marketplace or a POS location gets its own account when you want it reported separately. |
| The payment | The shopper paid in the cart, so the order imports with a pre-payment for the full amount attached. The invoice consumes it. Nothing is charged in AIMS360; refunds are issued in the cart and recorded against the account. |
| The discount | A cart discount arrives as one dollar amount on the order, not per line. If the order ships in two parts, you decide how much of it applies to the first invoice and the rest waits for the second. |
| The dates | A web order is due the day it is placed. A padding setting adds days to the completion date so intelligent allocation can hold a web order for units arriving this week instead of failing it against today's stock. |
| The warehouse | Either the warehouse Shopify assigned to each line, when locations are in use, or the preferred warehouse on the store's customer account. With multi-warehouse a virtual warehouse can hold the units reserved for online sales. |
| The shipping method | The service the shopper chose at checkout is mapped to an AIMS360 ship via, so the pick ticket and the label carry the service that was paid for. Local pickup maps to a pickup code. |
| The source | The order carries its source and, with tags mapped to accounts, the channel it came through, so views, batch picking and reports can filter web orders alone or one marketplace alone. |
| The status | Orders import as open. Only orders that are paid and unfulfilled import at all, which is why the checkout is set never to auto fulfill, and why an order paid only by gift card, which Shopify marks fulfilled, does not import. |
From here it is an order like any other: the same pick ticket, the same style, color and size inventory, the same invoice and the same reports, filtered to the store's account when you want the channel alone.
Open to sell for the warehouse tied to each Shopify location is pushed to the store on an OTS template that decides what counts: stock, allocations, and work in progress due within a window you set. With the automation the sync is live, and negative open to sell is sent as zero.
The cart takes the card. The order is paid and, with the checkout set never to auto fulfill, unfulfilled, which is the state AIMS360 imports. An order that arrives authorized rather than paid is retried until the status catches up.
The automation writes it to a staging table and creates the AIMS360 order on the store's account: 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, completion date padded if you chose to.
Immediately, for the units on the order, and exported to your warehouse system, your 3PL or your shipping app. Intelligent allocation can reserve the units by rule first, and a padded completion date lets it wait for stock due this week.
From your warehouse, a store that holds the units, or a 3PL that returns a shipped confirmation. The shipment is created, the pick ticket carries tracking, cartons, weight and freight, and the invoice consumes the pre-payment.
The order is fulfilled in Shopify with the tracking number, the shopper gets the shipping notification, and the inventory sync reflects the units that left. Every step is a logged workflow you can read and re-run.
Styles exported from the style master, open to sell pushed per location, orders imported paid, fulfillment and tracking sent back. More than one store connects to one company.
A marketplace channel connected to Shopify imports like any other order. A tag maps it to its own customer account, so it reports as its own channel while the source stays Shopify.
Fulfilled by merchant orders come through Shopify with their own flag for review. FBA orders download from Amazon into orders, pick tickets and invoices so units Amazon ships still leave your books.
Each store a location and a warehouse; register sales imported, picked and invoiced automatically, returns and exchanges at the register posted as RMAs and credits, pickup and ship from store for web orders.
A connected returns app sends the return into AIMS360 for the return authorization, the stock receipt and the credit memo, with the refund issued in the cart.
Wholesale buyers order through the B2B portal, the rep app or a wholesale Shopify store of their own; AIMS360 does not carry retail and wholesale prices in one store at the same time.
How each of these ships, beside wholesale DC orders and retailer dropship, is on multi-channel distribution; how they all enter one order pool is on multi-channel order management.
| Case | What AIMS360 does |
|---|---|
| Full shipment | The invoice consumes the pre-payment and the order closes. The account shows the invoice and the payment against it, zero balance. |
| Partial shipment | Invoice what shipped, applying the share of the discount you choose. The remaining units stay open for a second shipment, with the remaining discount and pre-payment balance waiting for it. |
| Cancel the balance | If the rest will never ship, cancel the remaining units from the order rather than deleting anything, so the link to the cart order stays intact and the canceled units report as canceled. |
| Refund the difference | Release the unused pre-payment, which becomes a credit memo on the account, post a receivables adjustment against that credit to record the refund, and issue the refund itself in the cart, which is where the card was charged. |
| Payment pending orders | Not recommended for consumer stores. If they are imported, terms and an order reason code flag them for review, because the automation does not check payment before it picks and ships. |
| Returns | A return through a connected returns app, or at a store register, creates the return authorization, receives the unit and issues the credit memo. Anything else is entered as an RMA by hand against the original invoice. |
All of it lands on the store account's receivables tab: the invoice, the pre-payment applied, the credit memo for a released balance and the adjustment that records the refund, so a month of web sales reconciles line by line against the cart's payouts.
The checkout must not auto fulfill, and an order paid only by a gift card, which Shopify marks fulfilled on its own, does not import. Payment pending orders can be imported but are not recommended for a consumer store, because the automation picks and ships without checking payment.
AIMS360 records the pre-payment, the invoice, the credit and the refund adjustment; the charge and the refund themselves are done in the cart. That is by design, and it means a refund is two steps: one in the cart, one on the account.
Shopify does not split a single order line across locations. The choice between one product per style with variants, which carries a variant limit, and one product per color is made when the store is connected and cannot be changed without reconnecting.
The connection works on every Shopify plan. The one thing a single store cannot do is carry retail and wholesale prices from AIMS360 at the same time; a wholesale store is its own connection.
Selling to consumers through your own web store, marketplaces and stores from the same order pool, inventory and books that run your wholesale business. Consumer orders download from the cart, become orders on a customer account for the channel, pick from the warehouse that holds the units, ship from your warehouse, a store or a 3PL, invoice against the payment already taken, and fulfill back to the cart with tracking. The styles, colors, sizes, costs and reports are the ones the wholesale side already uses.
Your Shopify web store, more than one Shopify store if you run several, marketplace channels connected through Shopify, Amazon fulfilled by merchant through its own connection, Amazon FBA, and Shopify POS for physical stores. Orders from all of them arrive in the same customer orders module with a source on each.
The store is connected once; from then on the automation downloads every paid, unfulfilled order into a staging table and creates the AIMS360 order on the store's customer account, with the shopper as bill to and ship to, the pre-payment attached, the discount as an amount, the shipping method mapped to a ship via and the warehouse from the Shopify location or the account. A starting order number decides where the import begins on a store that already has history.
Because a consumer is a ship to, not a trading relationship. Thousands of shoppers as accounts would bury the wholesale customer list and every report. One account per store or channel keeps consumer sales reportable as a channel, and the shopper's details still sit on every order, invoice and label.
AIMS360 pushes open to sell to the store from the warehouse tied to each location, on an OTS template that decides what counts: stock, allocations, work in progress due within a chosen number of days. With the automation the sync is live, so a wholesale pick reduces what the web store can sell within minutes. Sending zero when open to sell is negative stops the cart selling units you do not have.
Yes. With multi-warehouse, a virtual warehouse can hold the units reserved for the web store and be the warehouse tied to the store's location, so wholesale picking cannot take them. Intelligent allocation can also reserve units to web orders by rule, and the completion date padding lets it hold a web order for units arriving this week.
The shopper pays in the cart. The order imports with a pre-payment for the full amount, the invoice consumes it, and the account 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 the card.
A cart discount arrives as a single dollar amount on the order. On a full shipment it applies to the invoice as is. On a partial shipment you set how much of it applies to the first invoice, and the remainder stays on the order for the balance.
Yes. A store location allowed to fulfill web orders can ship the order or be a pickup point, and any warehouse can be a 3PL that receives the pick ticket and confirms the shipment. The DTC fulfillment automation page covers the four places a consumer order can ship from and the automated chain between them.
The fulfillment with the tracking number, which is what triggers the shopper's shipping notification, and the inventory sync. A pickup order is best marked picked up in Shopify rather than shipped. Store sales are marked fulfilled without the email.
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. 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. The refund to the card is issued in the cart.
They run through the same pick ticket, and the automation creates it the moment the order imports, exports it to your warehouse or 3PL and invoices when the shipment is confirmed. Batch picking offers a view that leaves automated web orders out, so a manual run never collides with the automation. A web order can also be padded so intelligent allocation treats it like any other order with a date.
More than one Shopify store connects to one AIMS360 company, each with its own name, its own exported styles and its own customer account if you want separate reporting. Inventory is not split per connection unless you use multi-warehouse. One store cannot carry both retail and wholesale prices from AIMS360 at the same time; a wholesale store is its own connection, and the B2B portal is the other route for wholesale buyers online.
Exported from the style master, either as one product per style with colors and sizes as variants, or as a product per color, a choice made once when the store is connected. Products already in the store are mapped to styles once. Scope decides whether a style is available online, at the register or both.
Every Shopify plan, Basic through Shopify Plus, and Shopify POS with it. What changes with Plus is scale rather than the connection: expansion and international storefronts, and Shopify B2B, which is a Plus feature. Shopify Plus wholesale stores have their own setup.
Every import is a logged workflow. A failure names its reason: still authorized rather than paid, a shipping method without a ship via mapping, terms missing on the account, a style not mapped. Fix it and re-run, or let the template's scheduled re-run pick it up; an order whose payment status catches up a few minutes later imports on its own.
Yes. A consumer invoice carries the style cost from the same style master, posts to the same receivables and the same ledger integration, and appears in the same sales, margin, style and season reports as a wholesale invoice, filtered to the store account when you want the channel alone. The receivables tab on the store account shows every sale, payment, credit and refund adjustment.
It does not charge or refund cards, it does not import orders that are unpaid, auto fulfilled or paid only by gift card, it does not split one order line across two locations, it does not carry retail and wholesale prices in one store at once, and the choice between one product per style and one per color is made once per connection.
The paid ones, the partial ones and the returns. We will run them through in a demo and show you the books and the cart afterward, side by side.
