B2B Wholesale Integrations · Updated September 2026
B2B wholesale platform integrations for apparel ERP: every platform your retailers buy on, one AIMS360 order book
Your buyers write orders on JOOR, NuORDER, RepSpark or Brandboom. New retailers find you on Faire or FashionGo. Trade accounts check out on Shopify B2B. Amazon sends a purchase order over EDI. Your own accounts log in to your portal, and your reps write on an iPad in the showroom. AIMS360 connects to all of it, publishes one open to sell figure to each, and imports every order into the same customer orders module, against the same inventory, on the same books.
AIMS360 integrates with nine B2B wholesale platforms: JOOR, NuORDER, RepSpark and Brandboom through native API connections AIMS360 built and maintains; FashionGo through a scheduled API connection; Faire configured per program; Shopify B2B through the Shopify connection; Amazon Vendor Central over native EDI; and Brandwise through a scheduled file pickup. It also ships with its own B2B portal (WebLink) and rep app (RemoteLink). Styles, customers and open to sell go out to the platform; wholesale orders come back as AIMS360 sales orders with the rep attached; intelligent allocation keeps every channel drawing on one stock record. Which platform to use is decided by where your retailers already buy, not by the ERP.
Which B2B wholesale platforms integrate with AIMS360?
Nine, and they connect in four different ways. How a connection is built decides how fresh the availability is and how fast an order arrives, so the mechanism is in the table alongside the platform.
| Platform | What it is | How it connects to AIMS360 | Orders arrive |
|---|---|---|---|
| JOOR | Wholesale management platform where brands and retailers write, review and manage buys; AIMS360 is listed on JOOR's technology partners page. | Native API integration built and maintained by AIMS360. Styles and linesheets, customers and open to sell by size and warehouse go out, including negative immediate stock and work in process with delivery dates. | Automatically, as live orders, with per order validation. |
| NuORDER by Lightspeed | B2B commerce platform used by brands and the retailers that buy from them. | Native REST API integration built and maintained by AIMS360. Products, customers and inventory go out; on hand, work in process and pre-book are all published; warehouses are mapped individually. | Automatically, as the order is written; inventory changes surface within minutes. |
| RepSpark | B2B wholesale ecommerce platform: branded digital catalogs, buyer self service ordering, event microsites and customization. | Native integration. Styles, colors, sizes and images, available to sell by size, and customer accounts with price groups and terms go out; invoices and tracking go back. | As AIMS360 sales orders with the rep attached. |
| Brandboom | Linesheet and order capture tool used by wholesale sales reps. | Event driven. Products with size variants, images and descriptions, and inventory go out; customers stay in step both ways; orders arrive by webhook and are held with the reason if they fail. | The moment the order is placed. |
| Faire | Wholesale marketplace connecting independent brands with independent retailers; Faire funds the retailer's net 60 terms and pays the brand. | Configured to your program during implementation. Orders land in one queue beside every other channel and availability is published from the same stock record with commitments netted out. | Continuously, shaped like ecommerce orders. |
| FashionGo | Online wholesale marketplace for apparel and accessories. | Sales channel connected over FashionGo's API. Existing FashionGo listings are mapped to AIMS360 styles by size; orders download and import on a schedule; a confirmation goes back once the order is fully allocated; inventory is updated from an OTS template. | On the schedule you set, then imported and allocated. |
| Shopify B2B | Shopify's built in wholesale feature on Shopify Plus: company profiles, price lists, catalogs and payment terms in the store admin. | Through the Shopify connection. Styles and open to sell per location go out; B2B orders come back like any Shopify order; fulfillment and tracking are sent back. | In real time through the Shopify order sync. |
| Amazon Vendor Central | Amazon's first party wholesale program: Amazon issues the purchase order, owns the goods and sets the retail price. Invite only. | Native EDI, run in house: 850 in, 855, 856, 810 and 846 out, 860, 820 and the 753 and 754 routing pair, all on the same record as your other EDI retailers. | As 850 purchase orders. |
| Brandwise | Order management platform used by sales rep agencies. | Scheduled file pickup. Orders exported from Brandwise are dropped in a folder, picked up on a schedule and imported through the AIMS360 API, with an email on any error. Orders in only; nothing goes back. | On each scheduled pickup. |
The two you do not integrate at all
WebLink is the AIMS360 B2B portal: your accounts log in to your own site, see the collections you opened to them and place their own orders, with no public prices and no self signup. RemoteLink is the rep iPad app: the line with images, sizes, colors and open to sell, quantities keyed in front of the buyer, a signature, and the order in AIMS360 with no re-keying, working with the wifi off. Both are part of AIMS360 and share the same collections.
Another platform in place?
A platform that exports orders to a spreadsheet loads through the AIMS360 order import. One that can drop a file on a server is picked up on a schedule, the Brandwise route. One with its own API connects through the AIMS360 Open API, which exposes the same style, customer, inventory and order records the connectors above use, as a scoped project. None of the connections is switched on by a marketplace toggle; each is activated and mapped with the AIMS360 team.
How do JOOR or NuORDER orders get into AIMS360 automatically?
The same six steps run on every platform connection. What changes is the trigger in step five, and that is what separates a native API connection from a file that gets collected overnight.
- Connect and map once. The connection is activated with the AIMS360 team. Styles, colors and size scales, customer accounts, price groups and terms, and warehouses are mapped between the platform and AIMS360. The account each channel imports against carries terms, ship via and a sales rep, which is what stops orders failing validation later.
- Publish the line. Styles with their colors and sizes, images and descriptions, and on JOOR the linesheets with season and delivery dates, are created on the platform from the AIMS360 style master. The line the buyer sees is the line the ERP will ship.
- Publish availability. Open to sell is calculated by an OTS template from stock, allocations and, if you choose, work in process due within a window, and published per warehouse. JOOR gets negative immediate stock and work in process with its delivery date. NuORDER gets on hand, work in process and pre-book. The others get open to sell from the same record.
- The rep or buyer writes the order on the platform, against that line and that availability, with the account's own pricing and terms where the platform carries them.
- The order imports. AIMS360 creates a live sales order on the mapped customer account with the rep attached. On JOOR and NuORDER the import is automatic through the API. On Brandboom a webhook fires as the order is placed. On FashionGo the download and import run on the schedule you set. Anything that fails validation is held in a failed import view with the reason, fixed for one order or every selected order at once, and imported again.
- Allocate, ship, invoice, report back. Intelligent allocation reserves units by rule, the order picks, ships and invoices like any other, and where the platform supports it the status goes back: invoices and tracking to RepSpark, a confirmation to FashionGo once the order is fully allocated, fulfillment with tracking to Shopify B2B, the 856 and 810 to Amazon.
Why the trigger matters. A file collected on a timer means the order exists in one system and not the other until the next run, and a malformed file fails quietly. A native API call or a webhook means the order lands as it is written, a failed one is held with its reason, and every run is logged as a workflow in AIMS360 that you can read and re-run. That is the difference buyers notice as fewer oversells and fewer "did you get my order" emails.
What moves between AIMS360 and each platform, and in which direction?
Each row is what the live integration is documented to do. Where a platform has no documented path for something, the cell says so rather than guessing; your implementation manager confirms scope for your program.
| Platform | Line out (styles, images, linesheets) | Availability out | Customers | Orders in | Back to the platform |
|---|---|---|---|---|---|
| JOOR | Yes, with linesheets, season and delivery dates | Yes, by size and warehouse, negatives and dated WIP | Yes, out to JOOR | Yes, automatic via API | Export status per order |
| NuORDER | Yes, products | Yes, on hand, WIP and pre-book, per warehouse | Yes, out to NuORDER | Yes, automatic via API | Run logs; no tracking path documented |
| RepSpark | Yes, styles, colors, sizes, images | Yes, available to sell by size | Yes, with price groups and terms | Yes, with the rep attached | Yes, invoices and tracking |
| Brandboom | Yes, with size variants, images, descriptions | Yes, committed units netted out | Yes, both directions | Yes, by webhook as placed | Failed orders held and retried; no tracking path documented |
| Faire | Per program | Yes, from one stock record, commitments netted | Faire retailers order through Faire | Yes, into one queue | Faire handles payment; no invoice cycle |
| FashionGo | Existing listings mapped to styles by size | Yes, on an OTS template, scheduled | One default account for all FashionGo orders | Yes, scheduled download and import | Yes, confirmation once fully allocated |
| Shopify B2B | Yes, through the Shopify connection | Yes, per Shopify location | Company profiles live in Shopify | Yes, real time order sync | Yes, fulfillment with tracking |
| Amazon Vendor Central | No, Amazon buys from its own catalog | Yes, 846 for Direct Fulfillment | Amazon is the account | Yes, 850 purchase orders | Yes, 855, 856, 810, 997 |
| Brandwise | No | No | Orders carry a Brandwise user code | Yes, scheduled file pickup | No, one way |
Whatever the platform, the order that lands is the same AIMS360 order: a size run across the style, color and size grid, the account's price and terms, a start and cancel window, and a sales rep, so commissions, factor approvals and credit limits apply the same way they do to a keyed order. The B2B wholesale orders page follows the order from there.
Do you need JOOR if you have your own portal? Portal, rep platform, marketplace or EDI
These get bundled together as "B2B software" and they answer different questions about who is buying and where they want to buy. The choice between them is covered properly in the wholesale B2B platforms guide; what belongs on this page is how each route lands in AIMS360, because that is what makes running several at once workable.
| Who is buying | The route | How it lands in AIMS360 |
|---|---|---|
| Accounts you already have | Your own WebLink portal and the RemoteLink rep app, both part of AIMS360 | No integration. The order is written in AIMS360's own tools against the same collections and open to sell. |
| Retailers who buy across brands in one tool | JOOR or NuORDER, because the buyer is already there | Native API. Line and availability out, orders in automatically, held with a reason if they fail. |
| Your reps, with catalogs and self service for their accounts | RepSpark or Brandboom | Native connections. Orders in with the rep attached; RepSpark also gets invoices and tracking back. |
| Retailers you do not have yet | Faire or FashionGo, for a commission | Faire per program into one queue; FashionGo on a schedule with a confirmation back once allocated. |
| Trade accounts on your Shopify Plus store | Shopify B2B | Through the Shopify connection, real time, fulfillment and tracking back. |
| Department stores, big box and Amazon | EDI, because the retailer mandates it | 850 in, 855, 856 and 810 out, run in house on the same record as the platform orders. |
So: you need JOOR when your retailers buy on JOOR, and a portal does not change that. Most AIMS360 brands run two or three of these routes at once, and the reason it works is that every one of them imports into the same order book. The choice is commercial. The integration makes sure it is not also an operational one.
One inventory, one price structure, one set of rules across every channel
The point of connecting the platforms to the ERP rather than running them beside it is that the things a wholesale order depends on live in one place.
| Shared record | What it does across channels |
|---|---|
| Open to sell | One OTS template decides what counts, stock, allocations and work in process within a window, and that figure is published to every platform per warehouse. A JOOR order, a Faire order and an EDI purchase order draw on the same units, so no platform thinks it has the whole pile. On JOOR, oversold immediate stock is sent as a negative so future availability stays honest. A virtual warehouse can hold units back for one channel. |
| Allocation | Intelligent allocation reserves stock and incoming work in process against orders by rules you set, including warehouse, start and complete dates, customer priority and order source, so the order that needs the units gets them rather than the pick that happens first. On FashionGo the confirmation back to the marketplace fires only when allocation reaches one hundred percent. |
| Pricing | The customer account carries the price tier and terms; RepSpark receives price groups and terms per account; Shopify B2B uses its own price lists per company; JOOR and NuORDER receive the wholesale and portal prices per active currency when multi-currency is on. One price structure, presented the way each platform presents it. |
| Credit and payment | Credit limits, factor approvals and assignments and terms apply to a platform order the same way as a keyed one. Card and ACH payment and net terms financing are available on the AIMS360 side; on Faire the marketplace handles the money. |
| Reps and commissions | The rep comes in on the order from the platform, and commissions are calculated on the posting date of the invoice, so reps are paid on shipped and invoiced sales regardless of which platform the order was written on. |
| Fulfillment | Every platform order runs through the same pick tickets, warehouse, scanning, shipping labels and 3PL connections. How each channel ships is on multi-channel distribution; the unattended version is automated order processing. |
What the B2B integrations do not do
Stated plainly, because these are the questions that surface in month two.
| Constraint | Detail |
|---|---|
| They do not replace the platform | Linesheet design on JOOR, retailer discovery on Faire, buyer self service on RepSpark and the checkout on Shopify B2B happen on the platform. AIMS360 feeds them and takes the orders back; it does not reproduce their front end. |
| Not every platform reports back | Invoices and tracking go back to RepSpark, fulfillment to Shopify B2B, a confirmation to FashionGo and the EDI documents to Amazon. JOOR shows an export status per order and NuORDER logs each run; neither has a documented tracking path. Brandwise is one way in. |
| JOOR orders land on the account's default warehouse | An inbound JOOR order is created against the warehouse on the AIMS360 customer template rather than the warehouse named on the JOOR order. Plan the templates accordingly. |
| FashionGo mapping is by hand | Existing FashionGo listings are mapped to AIMS360 styles size by size before the first order can import, and a listing left unmapped fails the import until it is. |
| Marketplace money stays with the marketplace | Faire pays the brand and funds the retailer's terms, so there is no invoice cycle to run; AIMS360 keeps the operational and accounting record of what shipped and what was paid. |
| Shopify limits | Shopify B2B needs Shopify Plus, and a single Shopify store cannot carry both retail and wholesale prices from AIMS360 at the same time; a wholesale store is its own connection. |
| Not self serve | Every connection is activated and mapped with the AIMS360 team, and the account each channel imports against needs terms, ship via and a rep before orders will import cleanly. Platform fees and commissions are the platforms' own and are not set by AIMS360. |

B2B wholesale integration questions, answered
Which B2B wholesale platforms integrate with AIMS360?
Nine today, plus the two AIMS360 builds itself. Native API connections built and maintained by AIMS360 for JOOR, NuORDER, RepSpark and Brandboom; a scheduled API connection for FashionGo; the Shopify connection for Shopify B2B; a per-program connection for Faire; native EDI for Amazon Vendor Central; and a scheduled file pickup for Brandwise. AIMS360 also has its own B2B wholesale portal (WebLink) and sales rep iPad app (RemoteLink), which share collections and need no integration at all. Every route lands orders in the same customer orders module against the same stock record.
How do JOOR or NuORDER orders get into an ERP automatically?
Through the platform's own API, with no file drop in the middle. AIMS360 publishes styles, linesheets or catalogs, customers and open to sell to the platform, so a rep or buyer writes the order against the line and availability the ERP knows about. When the order is saved, AIMS360 imports it as a live sales order on the right customer account with the rep attached, validates it, and holds anything that fails with the reason recorded so it can be fixed in bulk and re-run. On JOOR and NuORDER that is a direct API integration AIMS360 wrote and maintains; on Brandboom it is event driven through webhooks; on FashionGo it runs on a schedule you set. Every run is logged as a workflow in AIMS360.
Do I need JOOR if I already have my own B2B wholesale portal?
Only if your retailers buy on JOOR. A portal such as WebLink is where the accounts you already have log in, see the collections you opened to them and reorder; nobody can find you there. JOOR, NuORDER and RepSpark are where certain retailers, especially department stores and larger specialty chains, prefer to write and manage their buys across every brand they carry, so a brand joins because its buyers are already there. Marketplaces such as Faire and FashionGo add retailer discovery on top. Most AIMS360 brands run more than one: the portal and rep app for house accounts, a platform for the accounts that live on it, EDI for the majors. Because all of them import into one order book, the choice is commercial, not technical. The wholesale B2B platforms guide walks through that choice.
JOOR vs NuORDER: which one should a clothing brand use?
From the integration side, both are native API connections that AIMS360 built and maintains, both publish styles, customers and availability, both import orders automatically, and both handle several warehouses and work in process. The differences that show up in the integration: on JOOR, AIMS360 sends open to sell by size and warehouse including negative immediate stock and work in process with its delivery date, so a buyer choosing a later delivery sees future availability netted correctly; on NuORDER, availability covers on hand stock, work in process and pre-book before production exists, and inventory changes surface within minutes. The deciding factor is almost always which platform your key retailers already buy on, and what each platform charges, which is a conversation with the platform rather than with us; the guide compares the two in more depth.
Does Shopify have wholesale B2B built in, and how does it connect to an ERP?
Yes. Shopify B2B is Shopify's built in wholesale feature on Shopify Plus: company profiles, price lists and catalogs per account, payment terms such as net 30, and saved payment methods, all in the same admin as the online store. It connects to AIMS360 through the same Shopify integration as your consumer store, so styles and open to sell go out per location and B2B orders come back as AIMS360 orders with fulfillment and tracking sent back. What Shopify B2B does not do is run the rest of the business: allocation against production, EDI to major retailers, warehouse, costing and accounting still sit in the ERP. One limit to plan for: a single Shopify store cannot carry both retail and wholesale prices from AIMS360 at the same time, so a wholesale store is its own connection. The Shopify B2B page has the detail.
What is the best B2B wholesale platform for an apparel brand?
The one your retailers already buy on. Brands selling to department stores and larger specialty retailers tend to end up on JOOR or NuORDER because the buyers write their orders there; a rep force that wants branded catalogs and buyer self service looks at RepSpark; reps who mainly present a linesheet and capture orders on the road look at Brandboom; a brand chasing new independent retailers lists on Faire or FashionGo and pays for the discovery; a brand with a Shopify Plus store and trade accounts can switch on Shopify B2B. The wholesale B2B platforms guide compares all of them, with costs. The question this page answers is different: whichever you pick, or however many, the orders, the availability and the books stay in one place in AIMS360.
How does AIMS360 stop the same units being sold twice across JOOR, Faire, Shopify and EDI?
Every channel reads from one stock record. Open to sell is calculated by an OTS template that nets stock, allocations and, if you choose, work in process due within a window, and that figure is what gets published to each platform per warehouse. Intelligent allocation then reserves units against imported orders by rules you set, including warehouse, dates, customer priority and order source, so an EDI purchase order, a JOOR order and a Faire order are competing for the same units inside the ERP rather than each platform thinking it has the whole pile. On JOOR the integration sends negatives rather than hiding them, so an oversold immediate quantity is netted from incoming work in process instead of being sold again.
Can AIMS360 publish work in process and pre-book availability to wholesale platforms?
On JOOR, yes: work in process is sent with its expected delivery date, so immediate and future availability show separately. On NuORDER, yes: on hand stock, work in process and pre-book before production exists are all published, and warehouses are mapped individually. On the Shopify connection, work in process counts when it falls inside the window on the OTS template. For RepSpark, Brandboom, FashionGo and Faire the availability published is open to sell from the same stock record; whether future dated units are included is confirmed with your implementation manager, because the platforms differ in what they can display.
How much does Faire cost a brand, and what does AIMS360 do with Faire orders?
Faire's published commission is 25 percent on the first order from a retailer Faire found you, 15 percent on reorders, 0 percent on retailers you bring yourself through Faire Direct, with an optional next day payout at around 3 percent; those are Faire's figures, so confirm the current rate card with Faire. Faire also funds the retailer's net 60 terms and pays you, so there is no invoice cycle to run. AIMS360 handles the operational side: Faire orders land in the same order queue as your EDI, portal and rep orders, availability is published from one stock record with commitments netted out, and picking, shipping and the accounting record run through the same warehouse and 3PL connections as everything else. The connection is configured to your program during implementation. Details on the Faire page.
Does the integration send invoices and tracking back to the platform?
It depends on the platform. RepSpark receives invoices and tracking so buyers check status themselves. Amazon Vendor Central receives the 856 advance ship notice and the 810 invoice by EDI, which is how a 1P relationship works. Shopify B2B orders are fulfilled back with tracking through the Shopify connection. FashionGo receives an order confirmation once the order is fully allocated. JOOR shows an export status per order and NuORDER logs each run. Where a platform has no documented return path for tracking, the order still carries it inside AIMS360 and on the customer's portal login.
What happens when an imported wholesale order fails?
It is held, not lost. An order that is missing something AIMS360 requires, typically terms, ship via or a sales rep on the account, or a style the platform has that AIMS360 has not mapped, fails validation and moves to a failed import view with the reason. From there you can set the missing value on one order or on every selected order at once and import again. On the automated connections every download, import, allocation and confirmation is a logged workflow you can read and re-run, and the platform pages describe the failure modes for each one. The usual prevention is to set terms, ship via and rep on the customer account the platform imports against before the first order arrives.
Can I connect a wholesale platform AIMS360 does not have a connector for?
Usually. Three routes, from simplest to most involved. Any platform that exports orders to a spreadsheet can be loaded with the AIMS360 order import. A platform that can drop a file on a server can be picked up on a schedule, which is how Brandwise is connected today, orders in only. And the AIMS360 Open API exposes styles, customers, inventory and orders, so a platform with its own API can be connected as a scoped project. None of the existing connections is switched on by a marketplace toggle either; each is activated and mapped with the AIMS360 team.
How is a B2B platform order different from an EDI order from a major retailer?
A JOOR, NuORDER or Faire order is written by a person on a platform and arrives as a sales order to allocate, pick, ship and invoice on your terms. An EDI order from a department store or big box retailer arrives as an 850 purchase order under the retailer's vendor agreement, and shipping it means routing guides, GS1-128 carton labels, an 856 advance ship notice before the freight lands and an 810 invoice, with chargebacks when any of that is missed. AIMS360 runs EDI in house for 350+ retailers beside the platform connections, so both kinds of order sit in the same queue and draw on the same inventory, but the compliance work only applies to the EDI side. The EDI retailers hub covers that side.
Bring us a day of wholesale orders
The fastest way to judge a platform integration is to watch your own orders cross: written on JOOR, NuORDER or RepSpark in the morning, sitting in one AIMS360 queue beside the EDI and portal orders by lunch, allocated against the same units. Bring a day's worth and we will run them.
Related AIMS360 pages
- B2B wholesale order management follows the order once it is in: the size run, the account price, the ship window, allocation and shipping.
- JOOR, NuORDER, RepSpark and Brandboom are the deep pages for the four native connections.
- Faire and FashionGo cover the two marketplaces, including Faire's published economics.
- Shopify B2B and wholesale and Amazon Vendor Central cover the Shopify Plus route and the 1P EDI route.
- WebLink B2B portal and RemoteLink rep app are the two selling surfaces built into AIMS360.
- Omnichannel orders is the features hub for every order channel, and omnichannel DTC is the consumer side of this page.
- EDI retailers lists the 350+ retailers that order over EDI rather than a platform.
- Wholesale B2B platforms for apparel brands is the guide to choosing between them, with what each costs.
- Most popular apparel software integrations shows where the wholesale platforms sit beside Shopify, QuickBooks and the 3PLs.
- B2B wholesale payment processing covers taking cards and net terms on wholesale orders.
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. Faire commission figures and the NuORDER by Lightspeed name are the platforms' own published information, not independently verified.






.webp)











