.png)
Updated November 4, 2026. First published August 5, 2024. Checked against the AIMS360 JOOR integration page and joor.com.
How do multiple JOOR brands connect to one ERP?
The setup follows the way JOOR itself is organized: one storefront per brand, each with its own buyers and its own API key. AIMS360 mirrors that with one JOOR site per brand.
- Decide divisions or companies
Brands that share books become divisions of one AIMS360 company; 36 divisions are standard. Brands that need separate accounting become separate companies. Your accountant should make that call before data moves.
- Add a JOOR site per brand
Under the third-party settings, the default JOOR site is renamed for the first brand and a new site is added for each further brand, each with that brand's JOOR API key.
- Assign divisions to each site
With more than one JOOR connection, each site gets its own divisions. The all divisions option is not used, so a style can only publish to its own brand's storefront.
- Map warehouses
Each AIMS360 warehouse maps to a JOOR warehouse by name, so availability is published per location, including a 3PL.
- Send customers, styles and linesheets
Wholesale accounts go to JOOR matched by customer code. Styles go by style or by style and color, with sizes, prices and linesheets created in AIMS360 with season and delivery dates.
- Publish open to sell
AIMS360 sends availability by size and warehouse, including negative immediate stock and work in process with its delivery date, so buyers see what can ship.
- Import orders automatically
Orders written on any brand's JOOR site or iPad app download into the one AIMS360 order book, ready for allocation, picking and invoicing.
What moves between JOOR and AIMS360?
| Data | Direction | What it carries |
|---|---|---|
| Styles and linesheets | AIMS360 to JOOR | Sizes, wholesale and retail prices, fabric content, country of origin, minimums, linesheet season and delivery dates |
| Customers | AIMS360 to JOOR | Currency, bill to and ship to, matched to JOOR connections by customer code |
| Open to sell | AIMS360 to JOOR | By size and mapped warehouse, negatives included, plus dated work in process |
| Wholesale orders | JOOR to AIMS360 | Discounts, order and event types, terms, ship via and sales rep |
Because every brand lands in the same order book, list views and reports can filter, group and compare brands side by side, by division or rep, without stitching exports together. Retailers that buy several of your labels stay one customer account, and a different rep can be paid on each label. The full flow is on the JOOR integration page.
Should you integrate JOOR with your ERP?
JOOR offers two routes: an API integration, where your system posts customers, styles and inventory and pulls orders back, and a flat file route with spreadsheets or files dropped in a folder, which JOOR positions for smaller businesses without an ERP. For one brand with a short line, files can be enough.
Integrate when any of these is true:
- You sell more than one brand on JOOR and want one order book and one stock record behind them.
- You oversell, or ship late because JOOR showed stock that was already promised to another channel.
- Someone re-keys JOOR orders into your system, or fixes terms, ship via and rep on each one.
- You sell the same styles on Shopify, through retailer EDI or through reps outside JOOR, and need one availability number for all of them.
JOOR describes itself as a digital wholesale platform founded in 2010, with more than 14,000 brands and 700,000+ buyers in 150 countries. It runs the selling: linesheets, virtual showrooms and order writing. AIMS360 runs what is behind it: inventory, production, the warehouse, EDI and financials.
Is JOOR reliable for syncing orders with an ERP?
The sync is as reliable as the controls around it. These are the ones AIMS360 applies to JOOR orders:
| Risk | Control |
|---|---|
| An order lands missing terms, ship via or rep | Orders are validated before import, and missing values can be applied to a whole batch at once |
| A buyer resubmits the same PO | A duplicate PO warning appears before the order lands |
| A buyer changes an order after import | Cancel it in AIMS360 and re-download the updated version, as long as nothing has been allocated, picked or shipped |
| Buyers order stock that is already sold | Open to sell includes negatives and dated work in process, not a flat quantity |
| A problem goes unnoticed | Export status in JOOR and logs in AIMS360 show what moved and what failed |
A few behaviors to plan for: inbound orders use the default warehouse on the AIMS360 customer template rather than the warehouse named on the JOOR order; new colors added to an existing style must be pushed to JOOR; and the integration creates new linesheets rather than editing existing ones in JOOR.
Is there wholesale software built for companies running several brands?
Yes, and the question to settle first is not the software but the structure. A company that owns several labels can run them as divisions of one AIMS360 company, with one set of books, or as separate companies on the multi-entity add-on with consolidated reporting. Both run on the same platform, and either way each brand can have its own JOOR storefront, Shopify stores and EDI retailers.
The multi-brand Shopify and wholesale guide walks through a worked example with two labels, two warehouses and a 3PL. For the other B2B platforms that connect the same way, see NuORDER, Brandboom and RepSpark.
Multiple JOOR brands: FAQ
Yes. In AIMS360 each brand gets its own JOOR site with its own API key and divisions. Styles, linesheets, customers and open to sell go to the right storefront, and orders from every storefront import into one AIMS360 order book.
No. AIMS360 wrote the integration against JOOR's own API and maintains it as part of the product, so there is no connector to license and nothing in the middle. AIMS360 appears on JOOR's technology partners page.
Usually yes once you run more than one brand or channel, oversell, or re-key JOOR orders. JOOR's flat file route suits a small brand without an ERP. An API integration keeps one stock record and one order book behind every channel.
With the right controls, yes. AIMS360 validates JOOR orders before import, warns on duplicate PO numbers, lets a changed order be re-downloaded before it is allocated, and publishes open to sell that includes negatives and dated work in process.
As divisions in one company, which share stock, warehouses and books and report sales, margin, WIP and receivables per division, or as separate companies with their own accounting. 36 divisions are standard.
Availability can be published per warehouse, including a 3PL. Inbound JOOR orders are created against the default warehouse on the AIMS360 customer template, not the warehouse named on the JOOR order, and can be changed on the order or per line.
Yes. If you sell in several currencies on JOOR, the same currencies are enabled in AIMS360 and orders import in the right currency. Currency is required on the customer and style exports.
NuORDER, Brandboom, RepSpark, Faire, FashionGo and Shopify B2B connect too, and AIMS360 has its own B2B portal and the RemoteLink iPad app for reps. All of them land orders in the same AIMS360 order book.
AIMS360 is not affiliated with JOOR; JOOR is a trademark of its owner. JOOR company figures come from joor.com as of November 2026.
