.png)
Updated November 4, 2026. The partnership news below was first announced in Los Angeles on August 23, 2017. The rest of the page describes how the integration works today.
Yes, WFX Cloud PLM connects to AIMS360. The two companies announced the integration on August 23, 2017, so that styles and materials built in WFX no longer had to be keyed into the ERP a second time. Today AIMS360 has a WFX module with five import screens: vendors, styles, materials, bills of materials and importer costing.
The connection runs one way, from WFX into AIMS360. A style comes across once its stage in WFX is set to Production. From there AIMS360 runs the vendor purchase orders, cut tickets, work in process, orders, inventory and invoices. Full field rules are on the WFX PLM integration page.
What WFX and AIMS360 announced in 2017
On August 23, 2017, WFX Cloud PLM and AIMS360 announced a standard connector between WFX's product lifecycle management software and the AIMS360 apparel ERP. The problem they named was duplicate setup. A brand would develop a style in PLM, then stop and build the same style, its materials and its costs again in the ERP, and do it again every time something changed.
"PLM is about quick and efficient product development. But companies have to call 'time-out' to manually setup styles and materials in their ERP system which slows things down and creates opportunity for error."
Jatin Paul, CEO of WFX, August 2017
Shahrooz Kohan, then COO of AIMS360 and now its CEO, said the two companies already shared customers in apparel, so a standard connector made sense for brands that wanted a best of breed approach to PLM and ERP, "from design all the way through sales orders, purchase orders, production, and more." The goals in the announcement were to remove duplicate entry, speed the path from concept to delivery and handle changes without retyping them.
WFX's 2017 press materials pointed to wfxondemand.com. WFX's website today is worldfashionexchange.com, where the company says it was founded in 2000 and builds cloud PLM, ERP and MES software for fashion.
How the WFX to AIMS360 integration works today
You enter the WFX login that WFX issued you on the WFX setup screen in AIMS360, map a few code lists once, then download new and updated records, review them and import. Nothing lands unseen. Each record type has its own screen.
| Record | What comes from WFX | Where it lands in AIMS360 |
|---|---|---|
| Vendors | Supplier name, address and contacts | The vendor list, ready for vendor purchase orders |
| Styles | Article code and name, size card, division, season, selling price, primary images | A style master with colors and sizes |
| Materials | Fabrics and trims linked to the styles | AIMS360 materials, created if they do not exist yet |
| Bills of materials | Fabric, trim and labor lines by style, color and size, with quantity and cost | The style BOM: fabrics and trims on the trims tab, labor on the labor tab |
| Importer costing | Supplier cost, freight, duty, other cost, wholesale and retail price | The importer costing tab, with FOB and sell price by color |
Importer costing is switched on with an AIMS360 specialist, because brands name their WFX cost sheets differently. If you already have styles, materials or vendors in AIMS360, the Automap step links incoming WFX records to them so you do not end up with two copies.
PLM vs ERP: which system owns what
A best of breed setup works when each system has a clear job. Keep a second working copy of a style anywhere else and the two drift apart.
| Area | Lives in WFX | Lives in AIMS360 |
|---|---|---|
| Design and development | Concepts, tech packs, sampling, fit and vendor comments | Nothing. AIMS360 does not author tech packs or run sample rounds |
| The product record | The article while it is being developed | The style everyone sells, buys and ships from after import |
| Materials and BOM | The BOM as the developer builds it | Raw material inventory, material POs and the BOM issued to production |
| Costing | The cost sheet | Importer costing on the style, used by margin reports |
| Production and selling | Nothing | Vendor POs, cut tickets, work in process, receiving, orders, allocation and invoicing |
Setting up the connection, in order
- Enter your WFX login
Open the WFX setup screen under Modules in AIMS360 and enter the credentials WFX issued you.
- Map divisions, seasons and size scales
All three are required. Match each WFX size card to the closest AIMS360 size scale. AIMS360 holds up to 23 sizes per scale.
- Map labor codes if you bring labor costs across
Enter each WFX labor code exactly as WFX has it and map it to an AIMS360 manufacturing operation.
- Import vendors, then styles, then materials
Only styles at the Production stage come across, and color and size are mandatory.
- Import the bills of materials last
The BOM refers to the other three, so it goes after them. You can change a BOM in WFX and re-import it to update the style.
- Test one style end to end
Import a few vendors and one finished style before you bring in a whole season.
Limits to plan for before a season
- One way only. WFX sends to AIMS360. Stock, orders and production status are not sent back to WFX.
- Deletes do not carry. Deleting a material in WFX does not remove it in AIMS360. Retire it in AIMS360 yourself.
- Codes are shorter in AIMS360. Vendor codes are 5 characters, color codes 2 to 5, material codes 2 to 6, style numbers 3 to 15 with the hyphen as the only special character. Agree a naming convention before styles are built.
- Attach the size card when the style is created in WFX. A card added later can leave the style without sizes, and it will not import.
- Name the labor section Labor. The WFX BOM section has to be named exactly that or labor costs will not import.
Is a best of breed PLM and ERP setup right for you?
Both WFX and AIMS360 are cloud software, so neither needs a server in your building. The question is whether your product team needs a dedicated PLM at all. A separate PLM pays off when you develop many styles a season, work with overseas vendors on tech packs and sample rounds, and have a design team that lives in that process every day. If you mainly reorder core styles or buy finished goods from a short list of vendors, the style, BOM and costing tools inside AIMS360 Production (PLM) may be enough on their own.
AIMS360 also connects to Centric PLM and BeProduct. WFX is the one with its own import screens inside AIMS360, documented record by record.
Frequently asked questions
Does AIMS360 integrate with WFX PLM?
Yes. AIMS360 has a WFX module that imports vendors, styles, materials, bills of materials and importer costing from WFX. You map divisions, seasons, size scales and labor codes once, then download, review and import records from inside AIMS360.
When did WFX and AIMS360 announce their partnership?
On August 23, 2017, in Los Angeles. The announcement described a standard connector so fashion companies would not have to set up styles and materials twice, once in PLM and again in the ERP.
Is the WFX integration one way or two way?
One way, from WFX into AIMS360. Nothing is sent back to WFX, so inventory, orders and production status stay in AIMS360.
What is wfxondemand?
wfxondemand.com was the web address in WFX's 2017 press materials. WFX's website today is worldfashionexchange.com. This page is AIMS360's and covers the integration; for WFX itself, contact WFX.
When does a WFX style import into AIMS360?
When its lifecycle stage in WFX is set to Production and it carries the required fields: article code, article name, size card, division, season and selling price. Color and size are mandatory.
Does WFX costing come across to AIMS360?
Yes, through importer costing, which an AIMS360 specialist switches on with you. Supplier cost becomes FOB and wholesale price becomes sell price, both by color. Freight, duty, other cost and retail price come across by style.
Will WFX create duplicate styles in AIMS360?
Not if you use Automap. If you already have styles, colors, materials or vendors in AIMS360, Automap links the incoming WFX records to the ones you have instead of creating new copies.
Is WFX cloud software?
Yes. WFX describes itself as cloud PLM, ERP and MES software for fashion. AIMS360 is also cloud software, hosted on Microsoft Azure, so the PLM to ERP handoff runs without servers on your side.
Sources
Checked November 4, 2026.
- WFX Cloud PLM and AIMS360, joint announcement, Los Angeles, August 23, 2017 (the original text of this page).
- World Fashion Exchange, About WFX (founded 2000; cloud PLM, ERP and MES software for fashion).
- AIMS360, WFX PLM integration (records, setup, code rules and limits).
Related reading
Updated November 4, 2026 by the AIMS360 team. Details of WFX come from World Fashion Exchange's own website on that date and should be confirmed with WFX. WFX is a trademark of its owner. AIMS360 is not affiliated with WFX.
Bring one production ready style with its BOM and cost sheet. We will show where it lands in AIMS360 and how it becomes a vendor PO and a cut ticket.
Book a free demoTalk to us
