Every wholesale order in one queue, however it arrived: typed in, written on JOOR, NuORDER, RepSpark or Brandboom, sold on Faire, ordered through Shopify B2B, or transmitted by a retailer over EDI. One inventory, one price structure, one order book.
A rep writes one on JOOR at market. A boutique places one on Faire. A department store transmits one over EDI at two in the morning. Someone emails a purchase order that gets typed in by hand. Four orders, four routes, and all four want the same mediums out of the same warehouse. AIMS360 puts them in one queue against one inventory, which is the only arrangement where the answer to "can we ship this" is a fact rather than an opinion.
It is handling orders from retailers who buy to resell, which behave nothing like a consumer buying one unit. A wholesale order carries a size run rather than a single size, a price specific to that account rather than a list price, a start and cancel ship window rather than "as soon as possible", and payment terms rather than a card charge.
Managing it means three things: capturing the order wherever it was written, committing real inventory against it so you are not promising the same goods twice, and shipping inside the window the buyer agreed to. AIMS360 does all three in one place, whichever of the five routes below the order came in on.
Most brands use three or four of these at once, and the trouble usually starts when each one keeps its own version of what is available.
A rep or a buyer writes the order on a digital linesheet. AIMS360 sends the line and the available quantities out, and the order comes back as a sales order with the customer and styles already attached.
A department store or chain transmits a purchase order as an EDI 850. It lands against live inventory, on their terms, with their routing guide waiting at the other end.
An independent retailer finds you on Faire and orders without any EDI relationship existing. Same order book, no trading partner setup.
Shopify B2B with company accounts and catalog pricing, where the buyer logs in to you rather than the other way around.
From a trade show, a phone call, or a purchase order that arrived as a PDF. Still the most common route at market, and the one where price categories and tiers do the most work.
All five end in the same place: one order book, one inventory, one set of ship windows, one commission calculation, one ledger. That is the whole argument.
Each of these is built by AIMS360 rather than licensed from a middleware vendor, which in practice means one subscription and one support queue rather than two of each. Each has its own page with the detail.
Retailer EDI is the seventh route and it works differently enough to have its own cluster: the EDI feature page covers the documents, and the retailer directory lists the connections. If you also sell direct, Shopify and Shopify Plus feed the same inventory.
Five things a consumer order does not have, and each one breaks something if the system was designed around a shopping cart.
| On a wholesale order | Why it matters |
|---|---|
| A size run, not a size | The line is 2 small, 4 medium, 4 large, 2 extra large, and it has to stay a matrix through picking, packing and invoicing. Flatten it into SKUs and every downstream document gets harder to read. |
| Start and cancel dates | A ship window, not a ship date. Early can be refused, late can be cancelled or charged back, and a retailer running EDI enforces both. The order book gets worked by window rather than by the date it was written. |
| A price for that account | Not a list price. The same style can carry different prices for different customers and different quantities, which is what price categories exist to handle. |
| Terms, not a card | Net 30, net 60, or a factor standing behind the receivable. The order has to survive a credit decision before it ships, and the money arrives weeks later through accounts receivable. |
| A rep behind it | Somebody gets paid for that order, sometimes two people splitting it. Commission calculates from the order itself rather than from a spreadsheet rebuilt at month end. |
Price categories and price tiers let one style carry many prices. A customer is assigned to a category. Base prices are set at the size level, so price by size works. Tiers apply better pricing at higher quantities, and an order splits across them automatically.
| What you can set | How it behaves |
|---|---|
| Price by account level | Categories named however you think, whether that is Level A, B and C or Wholesale and Retail. Assigned on the customer record, or in bulk across many customers at once. |
| Price by size | Because the base price sits at the size level, extended sizes can carry their own price without becoming a separate style. |
| Price by quantity | Tiers at 6, 12, 24 or whatever your breaks are. An order for 100 units splits by itself: 96 at the quantity 24 price, 4 at the base price. The order confirmation prints the breaks separately so the buyer can see the arithmetic. |
| A fallback order | Categories can be ranked, so if no price exists in the assigned category the system rolls down to the next one and finally to the style master wholesale price. Leave ranking off if you want a category to be the only price a customer ever sees. |
There is also a report for the question that follows, which is which orders went out below the standard wholesale price and to whom. That sits under sales reporting rather than in the order itself.
Every wholesale channel wants to know one thing: how many can I have. Answer it from a different place for each channel and you have built a machine for overselling, because nothing subtracts from anything else until a warehouse picker finds out.
The number a buyer should see is open to sell, which is stock plus work in process minus what is already committed. Not warehouse stock on hand, which ignores the orders already written against it. That distinction is why a brand can look fully stocked on a platform and still short ship, and it is the single most common way wholesale relationships get damaged.
Three things buyers reasonably expect from a wholesale page that are not in the product.
AIMS360 does not host a digital catalog, a buyer facing storefront or a wholesale selling surface of its own. That is what the platforms above are for. AIMS360 feeds them and takes the orders back.
Price categories and tiers apply to orders entered in AIMS360. Orders coming from a platform, a marketplace or EDI carry the price agreed on that channel. Stated here rather than discovered in month two.
No buyer discovery, no retailer database, no outreach tooling. Faire and the trade shows do that. AIMS360 handles what happens after a buyer says yes.
What brands ask when wholesale starts arriving from more than one place.
Handling orders from retailers who buy to resell, as distinct from consumers buying one unit. A wholesale order carries a size run rather than a single size, a price specific to that account, a start and cancel ship window, and payment terms. Managing it means capturing the order wherever it was written, committing real inventory against it, and shipping it inside the window the buyer agreed to.
Five ways, all landing in the same order queue. Written on a B2B platform such as JOOR, NuORDER, RepSpark or Brandboom and imported back. Transmitted by a retailer as an EDI 850 purchase order. Placed on a wholesale marketplace such as Faire. Ordered through Shopify B2B on your own storefront. Or typed straight into AIMS360 from a trade show, a phone call or an emailed PO.
JOOR, NuORDER, RepSpark and Brandboom for digital linesheets and buyer portals, Faire for the wholesale marketplace, and Shopify B2B for wholesale on your own storefront. Each is a native integration built by AIMS360 rather than a licensed third party connector, so there is no second subscription and no second support queue.
They draw on one master stock record, which is the point. A unit committed to an EDI purchase order is not also available to a JOOR buyer or a Shopify B2B account. Brands that run each channel on its own spreadsheet or its own platform inventory discover the problem at ship time, when two orders want the same mediums.
The ship window. The start date is the earliest the buyer will accept delivery and the cancel date is the latest. Shipping early can be refused, shipping late can be cancelled or charged back, and for a retailer running EDI both are enforced by their routing guide. Wholesale orders in AIMS360 carry both, so the order book can be worked by window rather than by order date.
Yes, through price categories and price tiers. A customer is assigned to a category, base prices are set at the size level so price by size is possible, and tiers apply better pricing at higher quantities. An order for 100 units can split automatically, with 96 priced at the quantity 24 tier and 4 at the base price. Categories can also be ranked so pricing falls back to a lower category, or to the style master wholesale price, when no tier price exists.
Not currently. AIMS360 documentation states the price categories and tiers feature works on manually entered orders within AIMS360 and is not linked to other integrations at this time. Orders arriving from a B2B platform, a marketplace or EDI carry the price agreed on that platform or on the retailer purchase order. Classic price sheets remain available, and for many brands the platform is where the negotiated price already lives.
Yes. Purchase orders and work in process are visible with expected dates, so orders can be written against production that is still at a factory or on the water. That is how seasonal wholesale has always worked, and it only stays honest if the system can see incoming goods rather than only warehouse stock.
Open to sell, which is stock plus work in process minus what is already committed, rather than warehouse stock on hand. Sending stock on hand to a B2B platform overstates what you can deliver, because it ignores the orders already written against it.
Yes. Orders carry their rep, and commissions calculate on sales orders, invoices and payments with flexible structures including multi-rep splits, whichever channel the order came from.
No, and mixing them up causes real problems. Shopify B2B is your own storefront with company accounts and catalog pricing, where the buyer comes to you. EDI is a retailer transmitting a purchase order on their terms, with their routing guide, labeling rules and chargebacks. Shopify is one sales channel among several, not the umbrella the others sit under.
No. AIMS360 does not host a digital linesheet, a buyer facing catalog or a wholesale storefront of its own. The B2B platforms do that, and AIMS360 feeds them the line and the available inventory and takes the orders back. If you want a selling surface, you pick one of those. If you want the order book, the inventory and the money behind it, that is AIMS360.
Last reviewed 19 August 2026 by the AIMS360 team. AIMS360 capabilities described here, including price categories and price tiers with pricing by customer account level, by size and by quantity purchased, automatic tier splitting across an order, category ranking with fallback to the style master wholesale price, and the reporting of orders sold at a discount or premium, reflect the pricing and order entry workflow as documented in the AIMS360 support knowledge base, which also states that price categories and tiers currently apply to manually entered orders rather than to orders arriving through integrations. Integration behaviour differs by platform and is described on each platform page. The four channel example in the opening is illustrative, not customer data. Your own configuration is set during implementation.
Whatever it arrived on. We will load orders from a platform, an EDI account and a hand-keyed PO, put them against one inventory, and show you what is actually shippable inside each ship window.
