Two-way Brandboom integration: AIMS360 creates linesheet products from your styles, keeps open to sell inventory current and imports Brandboom orders as sales orders.

AIMS360 connects to Brandboom in both directions. Styles publish to your linesheets with their colors, sizes, images and descriptions. Available inventory, including what's coming from production, updates as stock moves. Customer accounts stay matched. And every order a buyer or rep writes in Brandboom lands in AIMS360 as a sales order, ready to allocate, pick, ship and invoice.
By Shahrooz Shawn Kohan, CEO of AIMS360 · Updated November 6, 2026
Yes. AIMS360 has a native, two-way Brandboom integration, rebuilt in October 2026 on Brandboom's latest API. It creates Brandboom products from your AIMS360 styles with their colors and sizes, sends images and descriptions, keeps available inventory current from the open to sell (OTS) template you choose, including future availability from work in process, syncs customer accounts both ways, and imports Brandboom orders into AIMS360 as sales orders.
Updates move by webhook when something changes, so inventory and orders don't wait for an overnight file. AIMS360 is the consumer brands ERP that holds the stock record, so the quantity a buyer sees on your Brandboom linesheet is the same one your Shopify store, your EDI retailers and your warehouse work from.
Updated for the 2026 Brandboom integration release.
| Item | Detail |
|---|---|
| Integration type | Native AIMS360 integration through Brandboom's API, maintained by AIMS360 |
| Direction | Two-way |
| AIMS360 to Brandboom | Products with style, color and size variants, season and price tiers, images, descriptions, available and future inventory, and customer accounts |
| Brandboom to AIMS360 | Wholesale orders and customer accounts |
| How data moves | Event driven: webhooks fire when stock changes or an order is placed |
| Inventory sent | Open to sell from the AIMS360 OTS template you pick: available now, plus future availability from work in process by ship window. Sold-out items go to zero |
| Style matching | Auto map on style, color and size, reviewed and approved in bulk, or map by hand |
| Order header | Division, terms, ship via and sales rep filled in from the customer mapping |
| Duplicates | Checked before a product or an order is created |
| Failed orders | Held with the reason recorded and retried once the cause is fixed |
| Payment terms and ship via | Brandboom terms and shipping methods mapped to your AIMS360 terms codes and ship via |
| How you install it | From the AIMS360 App Store, then connect with your Brandboom API key |
| Where you manage it | The Brandboom app in the AIMS360 Runway web app, for users with the App Integration permission |
| Setup | With the AIMS360 implementation team |
| Other wholesale channels | Runs alongside JOOR, NuORDER, RepSpark, Faire, WebLink and RemoteLink on the same inventory |
Real time. The AIMS360 Brandboom integration is event driven. When stock changes in AIMS360, the new quantity goes out because the change happened. When a buyer places an order in Brandboom, it comes across because the order was placed. Nothing waits for a nightly run.
Brandboom also offers a scheduled file drop for ERPs that can export product and inventory reports. The AIMS360 integration uses Brandboom's API instead, which is how orders and customer accounts flow back into AIMS360 too.
| Scheduled file transfer | Event driven, what AIMS360 uses | |
|---|---|---|
| How data moves | Files written and collected on a timer, whether or not anything changed. | An update is sent when something changes in either system. |
| Inventory freshness | As fresh as the last file, often overnight. | Reflects the sale, receipt or allocation that just happened. |
| Overselling risk | Higher. Buyers can order stock that sold hours ago. | Lower. The linesheet tracks what is free to sell. |
| Order timing | An order waits for the next run, so it exists in one system and not the other. | The order lands as it is placed. |
| When something fails | A missed or broken file goes unnoticed until someone looks. | A failed order is held with the reason recorded and can be retried. |
A good question for any vendor: when a unit sells, what has to happen before the linesheet knows? If the answer is a schedule, you're looking at the first column.
Five kinds of data move between the two systems. Products, images and inventory go out, orders come back, and customer accounts travel both ways.
| Data | Direction | What it covers |
|---|---|---|
| Products and styles | AIMS360 → Brandboom | Style colors with their size variants, season and price tiers, created in Brandboom from your AIMS360 records, so the line shows as a size grid instead of a flat SKU list. Duplicates are blocked. |
| Images and descriptions | AIMS360 → Brandboom | Each color's images, with the style image used when a color has none, and descriptions from AIMS360. You choose whether AIMS360 images overwrite what's in Brandboom or keep it. |
| Inventory | AIMS360 → Brandboom | Open to sell from the OTS template you choose: available now plus future availability from work in process by ship window. Sold-out items go to zero. |
| Customers | AIMS360 ↔ Brandboom | Brandboom buyers imported into AIMS360 and AIMS360 customers pushed to Brandboom, linked in a customer mapping screen so each order lands on a real account. |
| Orders | Brandboom → AIMS360 | Orders written by buyers or reps, created as AIMS360 sales orders ready to allocate, pick, ship and invoice, with Brandboom payment terms and shipping methods mapped to your AIMS360 codes. |
The open to sell quantity from the AIMS360 OTS template you pick during setup. The integration sends that number for each style, color and size, and sends a new one when it changes. You set the rule once in AIMS360, and Brandboom follows it.
The template covers what's on hand now and what's coming. Future availability from work in process goes over by ship window, so buyers can order against later deliveries, not only today's shelf. When a style color sells out, AIMS360 sends a zero instead of leaving the old number up, and an inventory screen shows what was pushed to Brandboom and when.
Brandboom is rarely your only channel. The same units are on offer to Shopify shoppers, EDI retailers and buyers on other wholesale platforms. AIMS360 keeps one stock pool across all of them, and intelligent allocation decides who gets goods when supply runs short, so reps aren't selling units that are already promised.
Through a mapping table that links each AIMS360 style, color and size to its Brandboom product. That link is how inventory lands on the right item and how an incoming order finds the right style.
AIMS360 lists the styles that aren't in Brandboom yet. Select the ones you want, and AIMS360 creates them in Brandboom with their colors and sizes under the style, plus season and price tiers, then sends images and descriptions. New products are mapped as they're created. Nobody types style IDs or colors into Brandboom by hand.
If your line is already in Brandboom, filter your active, unmapped style colors and run auto map. It matches each one to a Brandboom product on style, color and size, and you review the matches and approve them together. If a product carries a different number in Brandboom, map it by hand. Conflicts and duplicates are flagged for you instead of being settled silently.
A missing match stops an order so someone can fix it. A wrong match ships the wrong garment. That's why matches are reviewed before they're saved.
When a buyer or rep places an order in Brandboom, a webhook sends it to AIMS360. Nobody exports a file, and there's no window where the order exists in one system and not the other.
Line items match your styles through the mapping, and the header comes from the customer mapping, with that account's division, terms, ship via and sales rep. The result is an AIMS360 sales order that allocates, picks, ships and invoices like any other, from your own warehouse, a 3PL or ShipStation. Since May 2026, Brandboom orders also match the right customer when Brandboom's usual customer field is empty, using a second customer code (see What's New).
Duplicate orders are caught instead of entered again. A double-entered wholesale order doesn't just inflate the order book, it holds stock another account could have bought.
If an order can't import, it's held with the reason recorded, usually a style that isn't mapped yet or a customer that isn't in AIMS360. Fix the cause and retry. Imported orders can be searched and filtered by status and date, so nothing quietly goes missing.
Seven steps, done with your AIMS360 implementation manager. Which options are switched on for your account is confirmed during implementation.
| Step | What you do | What happens |
|---|---|---|
| 1. Install the Brandboom app | Install it from the AIMS360 App Store. Once it shows as installed and active, Open Brandboom App appears in the Runway web app menu. | Users need the App Integration permission in AIMS360 to open it. Without it they see Access denied. |
| 2. Connect with your Brandboom API key | Enter the API key from your Brandboom seller account. | AIMS360 connects to that Brandboom account and shows the connection status. |
| 3. Pick the open to sell template | AIMS360 lists your OTS templates. Pick the one Brandboom should follow, and change it later if you need to. | Available quantities go out by style, color and size. |
| 4. Map payment terms and ship via | Match each Brandboom payment term, such as Net 30, and each Brandboom shipping method to an AIMS360 terms code and ship via. | Imported orders arrive with the right terms and shipping method. |
| 5. Map or create products | Filter your active, unmapped style colors. Auto map matches them to Brandboom products on style, color and size for you to approve, create new ones in Brandboom from AIMS360, or map an item by hand. | Every Brandboom product points to one AIMS360 style, color and size. |
| 6. Line up customers | Map Brandboom buyers to AIMS360 customer accounts, import new Brandboom buyers into AIMS360, or push AIMS360 customers to Brandboom. | Each imported order picks up that customer's division, terms, ship via and sales rep. |
| 7. Start taking orders | Share your linesheets the way you do today. | Orders import as AIMS360 sales orders, with import status and retry in one screen. |
AIMS360. It holds the inventory record and Brandboom shows it. When the two differ, AIMS360 is right, because it's the system that knows what's allocated to an EDI purchase order, reserved for an ecommerce drop, or picked and not yet shipped.
So if someone edits an available quantity directly in Brandboom, the next update from AIMS360 replaces it. Make availability changes in AIMS360 and let them flow out. If two AIMS360 styles look nearly the same, mapping is where that shows up, and it's better caught there than on a buyer's order. That's the job of an apparel and consumer brands ERP: one record every channel reads from.
Brandboom offers several ways to connect an ERP. They differ in what moves, which way it moves and who keeps the connection working. Checked against Brandboom's own pages on November 3, 2026.
An ERP connects to Brandboom in one of five ways: a pre-built integration, Brandboom's ERP product and inventory file sync, order export files, Zapier or a custom build on Brandboom's API, or a middleware partner such as Pipe17. AIMS360 is a pre-built integration that AIMS360 builds and maintains on Brandboom's API. It runs both ways, so Brandboom orders and new buyers come back into AIMS360 as sales orders and customers.
If buyers and reps write orders in Brandboom, pick a route that brings those orders back into your ERP so nobody re-keys them. If you only need your catalog and stock on the linesheet, a one-way product and inventory feed can be enough.
| Route | What moves | Who builds and maintains it | Brandboom source |
|---|---|---|---|
| Pre-built: AIMS360 | Products with colors and sizes, images, descriptions and open to sell inventory go to Brandboom. Orders come back as sales orders, and customer accounts sync both ways | AIMS360. It installs from the AIMS360 App Store | Listed under pre-built integrations in Overview of the API and Integration Options (April 8, 2026). Setup asks for a Brandboom Business plan: Set Up the AIMS360 Integration (March 19, 2026) |
| Pre-built: Shopify and ApparelMagic | Brandboom describes product, inventory and order fulfillment sync | Listed by Brandboom as its native integrations | Order Management page and Brandboom platform guide (verified July 31, 2026) |
| ERP product and inventory file sync | Products and inventory into Brandboom from report files your ERP schedules. Orders go back to the ERP through exports | Brandboom, on Business plans only | ERP Product + Inventory Sync (February 27, 2026) |
| Order export files | Orders out of Brandboom as CSV or Excel files, mapped to your ERP's import columns and imported on your side | Your team, each time you export | Order Management page |
| Zapier or a custom API build | Whatever the zaps or code are set up to move. Brandboom says these ERP connections take days or weeks | Your team or a developer | Order Management page |
| Middleware partner | Brandboom names Pipe17 for NetSuite and other systems | The partner | Brandboom integrations page |
Brandboom's plans, connectors and help articles change, so confirm the details for your Brandboom account with Brandboom. For how AIMS360 compares with other apparel ERPs on wholesale, see the wholesale B2B platforms guide.
Yes. AIMS360 also connects to JOOR, NuORDER, RepSpark, Faire and Shopify B2B, and includes its own buyer portal, WebLink, and iPad rep app, RemoteLink. Each one sells from the same AIMS360 stock record, so adding a channel doesn't mean splitting inventory.
| Platform | Where it fits | AIMS360 page |
|---|---|---|
| Brandboom | Fast digital linesheets, buyers who can order without an account, plus a marketplace | This page |
| JOOR | Where department store and specialty buyers already shop | JOOR integration |
| NuORDER | Buyer platform with live inventory in the buyer's view | NuORDER integration |
| RepSpark | Reps, dealers and logo programs, common in golf and team sports | RepSpark integration |
| Faire | Marketplace that finds small retail accounts, for a commission | Faire integration |
| Shopify B2B | Wholesale on the Shopify store you already run | Shopify B2B |
| WebLink | AIMS360's own B2B buyer portal | WebLink |
| RemoteLink | AIMS360's iPad app for reps at trade shows and on the road | RemoteLink |
Compare all eight in the wholesale B2B platforms guide.
What brands, ops teams and sales reps ask about running Brandboom with AIMS360.
Brandboom is a B2B wholesale platform for brands. You upload products, build digital linesheets and presentations, and share a link. Buyers browse the line and place orders, often without creating an account. Brandboom also runs a wholesale marketplace and offers a free plan and paid plans, listed on brandboom.com. Our line sheet guide covers how linesheets are used in wholesale.
Yes. AIMS360 has a native, two-way Brandboom integration, rebuilt in 2026. It creates Brandboom products from AIMS360 styles with their colors and sizes, sends images, descriptions and open to sell inventory, syncs customer accounts both ways, and imports Brandboom orders as AIMS360 sales orders. It is one of the B2B wholesale integrations AIMS360 maintains.
Brandboom's help center lists AIMS360 among its pre-built integrations, and Brandboom's integrations page lists AIMS360 as a partner integration. AIMS360 is built for apparel, footwear, accessories, beauty and other consumer brands. It keeps style, color and size grids intact in Brandboom, sends open to sell inventory by webhook, syncs customers both ways and imports orders as sales orders. The same system runs built-in EDI for 350+ retailers, Shopify and warehouse management. The other ways to connect an ERP to Brandboom are in the Brandboom ERP options table.
Three things: the Brandboom app installed from the AIMS360 App Store, a user with the App Integration permission in AIMS360, and the API key from your Brandboom seller account. Brandboom's help center lists its Business plan for the AIMS360 integration, so check your Brandboom plan first. Access is set in AIMS360 user permissions, and your implementation team can walk through the rest.
Products with their style, color and size variants, images, descriptions and available inventory go from AIMS360 to Brandboom. Wholesale orders come from Brandboom into AIMS360 as sales orders. Customer accounts sync in both directions, using the same AIMS360 customer records your other channels use.
Yes. AIMS360 sends each style color's images to Brandboom and uses the style image when a color has none of its own. Descriptions come from your AIMS360 product records. A setting decides whether AIMS360 images overwrite what is already in Brandboom or keep the existing ones. Images live with your AIMS360 product records.
Yes. It is event driven. A webhook sends an inventory update when stock changes in AIMS360 and sends an order to AIMS360 when it is placed in Brandboom, so neither side waits for a nightly file. From there, AIMS360 order management handles the order like one from any other channel.
The open to sell quantity from the AIMS360 OTS template you choose during setup, by style, color and size. That covers what is available now plus future availability from work in process by ship window, and a style color that sells out goes to zero instead of keeping an old number. AIMS360 keeps one stock pool for every channel, so the quantity reflects what is already promised to other orders. See style, color and size inventory.
Yes. Along with what is available now, the integration sends future availability from work in process by ship window, using the OTS template you pick in AIMS360. Brandboom gets quantities for later ship windows, not only what is on the shelf today. Production feeds that number through AIMS360 production tracking.
No. AIMS360 lists the styles that are not in Brandboom yet. Select them and AIMS360 creates the Brandboom products with their colors, sizes, season and price tiers, then sends images and descriptions. New products are mapped automatically, and duplicates are blocked, so a style cannot be created twice. Your style setup stays in AIMS360 styles and colors.
Through a mapping table that links each Brandboom product to an AIMS360 style, color and size. For a catalog that is already in Brandboom, auto map matches your selected style colors to Brandboom products on style, color and size, and you review and approve the matches in bulk instead of pairing hundreds of items one at a time. If a product carries a different number in Brandboom, map it by hand. Conflicts are flagged for you to resolve. Sizes follow your size matrix.
Yes. Brandboom sends each order by webhook as it is placed, and AIMS360 creates a sales order with the line items matched to your styles and the header matched to the customer account. Duplicate orders are caught instead of entered twice. From there it follows your normal B2B wholesale order flow.
Yes. In the Brandboom app settings you map each Brandboom payment term, such as Net 30, to an AIMS360 terms code, and each Brandboom shipping method to an AIMS360 ship via. Imported orders then carry the right terms and shipping method without anyone fixing them by hand. See AIMS360 shipping.
It is held with the reason recorded, not lost. The usual causes are a style that is not mapped yet or a customer that is not in AIMS360. Fix the cause and retry the order. Imported orders can be searched and filtered by status and date. Your implementation team walks through the orders screen during setup.
Yes, both ways. Brandboom buyers can be imported into AIMS360, and AIMS360 customers can be pushed to Brandboom. A customer mapping screen links each Brandboom buyer to an AIMS360 customer, by hand or from the sync. That mapping fills in the division, terms, ship via and sales rep on every imported order. If a buyer is not mapped yet, the order waits with a clear error instead of landing on the wrong account.
Like any other AIMS360 sales order. Allocate it, print pick tickets, then scan, pack and ship in the Runway web app, or send the order to your 3PL or ShipStation. Invoicing happens in AIMS360.
If you sell through more than one channel, usually yes. Brandboom is where buyers see your line and place orders. An ERP runs what comes next: inventory across channels, production and purchase orders, picking and shipping, retailer EDI, invoicing and accounting. AIMS360 does that for apparel and consumer brands and keeps Brandboom in sync. See the apparel ERP guide.
Yes. As accounts grow into bigger retailers, those retailers usually require EDI. AIMS360 has built-in EDI with 350+ retailers, so Brandboom orders and retailer purchase orders run through the same system and the same inventory.
The 2026 version was rebuilt on Brandboom's latest API. It creates Brandboom products from AIMS360 styles with season and price tiers, matches existing products on style, color and size for bulk approval, sends images and descriptions with an overwrite or keep setting, sends open to sell inventory by webhook including future availability by ship window, syncs customers both ways, maps payment terms and ship via, and imports orders with duplicate checks and retry. It installs from the AIMS360 App Store and runs from the Brandboom app in the AIMS360 Runway web app. Release notes are on What's New.
Updated November 6, 2026, for the 2026 Brandboom integration release. First published November 2024. Written by Shahrooz Shawn Kohan, CEO of AIMS360. Brandboom is a trademark of Brandboom, Inc. Which capabilities are enabled for your account is confirmed during implementation.
Bring a current linesheet to a 30 minute demo and see the same styles publish, count and come back as orders from one AIMS360 record.