Sell wholesale in NuORDER, run the business in AIMS360. A first-party, live API integration keeps styles, customers, inventory and orders in step in real time — including work-in-process and pre-book, so you can sell a season before production exists.
AIMS360 connects to NuORDER by Lightspeed through a direct, first-party REST API integration we built and maintain ourselves — no middleware connector in the middle. Inventory moves in real time, wholesale orders import automatically, and availability covers every scenario: on-hand stock, work in process, and pre-book before production even exists.
Talk to us about NuORDER Book a demoYes — and it is one of the most complete NuORDER ERP integrations available. Products, customers and inventory are pushed from AIMS360 to NuORDER, and wholesale orders written in NuORDER import back into AIMS360 automatically as live orders.
It is a native integration: AIMS360 wrote it directly against NuORDER's REST API and maintains it inside the product, so there is no middleware platform and no separately licensed connector between the two systems. Because it runs on the API rather than the flat-file route, inventory updates in real time and lands in NuORDER within minutes, and orders arrive as they are written rather than on a nightly run. NuORDER documents the connection on their own help desk, see NuORDER's AIMS integration article. The latest release adds pre-book selling and work-in-process inventory, so a season can be sold before a single unit is cut.
This is the part worth understanding before you compare platforms. NuORDER supports two ways for an ERP to connect: a REST API exchanging JSON, or flat files pushed over FTP/SFTP on a schedule. Both appear as "a NuORDER integration" on a vendor's website. They do not behave the same way.
| What AIMS360 usesREST API integration | Other ERPsFlat file over FTP / SFTP | |
|---|---|---|
| How data moves | Direct JSON calls between AIMS360 and NuORDER. | CSV or TXT files written to a server and collected on a set schedule. |
| Who built it | AIMS360, natively. Nothing to license, nobody in the middle. | Often a middleware vendor or outside integrator, billed separately. |
| Inventory freshness | Continuous. Changes surface in NuORDER within minutes. | As fresh as the last batch ran — often overnight. |
| Order capture | Automatic, as the order is written. | Collected on the next scheduled pull. |
| Overselling risk | Lower. Availability in NuORDER tracks what AIMS360 can actually commit. | Higher. Buyers can write orders against stock that sold hours ago. |
| Pre-book and work in process | Publishes on-hand stock, work in process, and pre-book before production exists. | Whatever the file happens to carry — usually a single on-hand quantity. |
| Warehouse detail | Multiple warehouses mapped individually, visible in both systems. | Typically a single pooled availability number. |
| Failure mode | Calls are logged per run, with export and inventory logs in AIMS360. | A missed or malformed file is silent until someone notices. |
To be fair about it: not every other apparel ERP uses flat files, and some do connect over the API. That is exactly why it is worth asking rather than assuming.
If you are evaluating another apparel ERP that advertises NuORDER support, the useful question is simply: API or flat file, and how often does inventory actually refresh? NuORDER's own integrations documentation sets out both patterns.
There is a second question worth asking, and it is about who actually wrote the integration. Plenty of ERPs reach NuORDER through an integration platform such as Celigo or Boomi, or through a connector built and sold by an outside integration vendor. That route works. It also puts a third product, a third invoice and a third support queue between your ERP and your line sheets.
The NuORDER connection is built into AIMS360, written directly against NuORDER's REST API. Nothing to license separately, no middleware subscription to renew, and one company accountable when inventory stops moving. NuORDER's own help desk records the connection as one AIMS360 developed on their API.
A connector platform sits between the ERP and NuORDER, with its own pricing, its own release schedule and its own support queue. When a sync breaks, the first job is working out whose problem it is — and every NuORDER or ERP update becomes a compatibility question for a vendor who answers to neither.
It is a fair question to put to any vendor: did you build this yourselves, or are we licensing somebody else's connector? The answer changes who you call at 6pm on the day a season goes live.
Four data flows, three out and one back, all over the same native API connection.
Style-colors with category, department and season mapping, dynamic style naming, brand ID, and price by size where you use it.
Wholesale accounts exported from AIMS360, with reps mapped between the two systems so every order lands with the right owner.
Availability by size and warehouse, updated continuously — on-hand stock, work in process, and pre-book where nothing is made yet.
Orders written by reps or buyers import automatically as live orders, with discounts, prepacks, order and event types and credit card processing.
Most ERP-to-B2B connections can only publish what is physically on hand. That is fine in the middle of a season and useless at the start of one. AIMS360 publishes availability across the whole picture.
What is on hand and open to sell right now, by size and by warehouse, refreshed continuously as counts, adjustments and orders move it.
Units in production and inbound. Buyers can commit against goods that are being made rather than waiting for them to land in the warehouse first.
Open a season and take pre-book orders in NuORDER before anything is cut. A recent release added this, so the line can be sold on plan rather than on stock.
Create multiple warehouses in NuORDER and connect each to a warehouse in AIMS360. Reps and buyers choose which warehouse's availability to view on a style, and the numbers reconcile with the matching AIMS360 warehouse.
AIMS360 keeps an Export Product Log and an Export Inventory Log, so when a style does not appear in NuORDER you can see exactly why rather than guess.
No nightly pull, no CSV round trip, no rekeying. Orders arrive in AIMS360 as they are written and are immediately ready for allocation, picking and invoicing.
Wholesale orders written by reps or buyers flow into AIMS360 on their own. New buyer? The AIMS360 customer can be created or assigned directly from the imported order.
Orders changed in NuORDER can be re-imported, and an order can be deleted and re-downloaded cleanly if something needs rebuilding.
Discounts and prepacks carry through, order and event types are respected, and credit card processing is supported on NuORDER orders.
Reps are mapped between the systems, so commission and account ownership stay correct on every order that lands.
Three things worth saying plainly, because finding them out mid-rollout is worse.
Images do not sync from AIMS360. Product photography is uploaded on the NuORDER side after products are exported. NuORDER supports batch image upload — plan for it rather than expecting AIMS360 to carry images across.
Inventory sync is switched on by our implementation team. It runs entirely through the API and has no settings screen inside AIMS360, so activation happens through Support and Implementation rather than a checkbox you tick yourself.
Turning on the API sync retires the legacy Push Inventory module. Once automated sync is active — particularly with multiple warehouses — the older manual push for NuORDER stops being available. That is the intended upgrade path, not a bug.
Everything runs from Modules → Third Party → NuORDER in AIMS360:
Set up categories and departments before exporting products, so styles land in the right place in NuORDER's navigation from the start.
Select styles by category, department and year, apply in bulk, and export. A saved view shows exported versus not-yet-exported active and inactive styles.
The live API inventory sync, including multi-warehouse mapping, open-to-sell settings, work in process and pre-book.
NuORDER orders flowing into AIMS360, with re-import for changes and full export and inventory logs alongside.
Yes. AIMS360 has a pre-built, first-party integration with NuORDER by Lightspeed built on NuORDER's REST API. Products, customers and inventory are pushed from AIMS360 to NuORDER, and wholesale orders written in NuORDER import back into AIMS360 automatically. NuORDER documents the AIMS360 connection as an API data connection on their own help desk.
It is native. AIMS360 wrote the integration directly against NuORDER's REST API and maintains it as part of the product, so there is no separate connector to license and no integration platform such as Celigo or Boomi sitting between the two systems. Some ERPs reach NuORDER through exactly that kind of middleware, or through a connector sold by an outside integration vendor, which adds a second subscription, a second release cycle and a second support queue. With AIMS360 there is one vendor accountable for the connection.
Yes. It is a live API integration, not a scheduled batch. Inventory changes in AIMS360 are pushed continuously and surface in NuORDER within minutes, and orders written in NuORDER import into AIMS360 automatically as they are placed. That is the practical difference between an API integration and a flat-file connection over FTP or SFTP, which typically refreshes on a much longer schedule.
Within minutes. The sync runs continuously rather than on a nightly or hourly batch, so any change to availability in AIMS360 — a physical count, a stock adjustment, a production receipt, or an order taken outside NuORDER — reaches NuORDER within minutes.
Yes. Wholesale orders written by reps or buyers in NuORDER import into AIMS360 automatically and in real time, arriving as live orders ready for allocation, picking and invoicing. Discounts, prepacks, order and event types and credit card processing all carry through, and edited orders can be re-imported.
Yes. A recent release added pre-book support, so brands can open a season and take pre-book orders in NuORDER before any production exists. You are not limited to selling what is already made or already cut — which is exactly what a pre-season wholesale line needs.
Yes. The integration covers the full range of inventory scenarios: current on-hand stock, work-in-process and future incoming inventory, and pre-book where no production exists yet. Availability published to NuORDER reflects what you can actually commit to sell rather than only what is sitting in the warehouse today.
Yes. You can create multiple warehouses in NuORDER and connect each one to a warehouse in AIMS360 through the API. Reps and buyers can then switch which warehouse's availability they are viewing on a style, and those numbers reconcile against the matching AIMS360 warehouse.
No. Images are uploaded on the NuORDER side after products are exported from AIMS360. NuORDER supports batch image uploads, and their support team can advise on the fastest route for a large catalog.
It is an activated module rather than something switched on from a settings screen. Our implementation team enables it, maps categories, departments, sales reps and warehouses with you, and runs the first product and customer exports alongside your team. Get in touch and we will scope it, and see how AIMS360 implementation works.
Yes. Price by size is supported in the AIMS360 to NuORDER product export, so size-differentiated pricing carries through to your NuORDER line sheets rather than needing manual maintenance on the NuORDER side.
NuORDER by Lightspeed is a B2B wholesale commerce platform used by apparel, footwear and consumer brands to present digital line sheets, take wholesale orders and manage buyer relationships. It handles the selling; AIMS360 handles inventory, production, warehouse, EDI and financials behind it.
We will walk through how your line sheets, inventory and wholesale orders would actually flow — including pre-book and work in process — and tell you honestly where the edges are, including the parts that are not automatic.
Get in touch Book a demo
