WFX is a cloud fashion PLM. AIMS360 imports WFX vendors, styles, materials, bills of materials and importer costing once a style reaches the Production stage. The connection is one way, WFX into AIMS360, with Automap for records you already have.

WFX is where a line gets planned, designed, specified and costed. AIMS360 is where the approved style becomes a purchase order, a cut ticket, an order book and a shipped carton. The WFX import modules inside AIMS360 carry vendors, styles, materials, bills of materials and costing across, so nobody re-keys a tech pack at the busiest point of the season.
Yes. AIMS360 has a WFX module with its own setup screen and five import screens: vendors, styles, materials, bills of materials and importer costing. You enter the WFX login WFX issued you, map divisions, seasons, size scales and labor codes once, then download new and updated records from WFX, review them and import. A style comes across once its lifecycle stage in WFX is set to Production.
The connection runs one way, from WFX into AIMS360. Nothing is sent back to WFX. If you already have styles, materials or vendors in AIMS360, the Automap step in the import screens links the incoming WFX records to the ones you have, so you do not end up with two copies. One thing to know before you start: this is AIMS360's page about the integration. For WFX itself, its documentation or its sign-in, go to worldfashionexchange.com.
Five record types, each with its own import screen. You download, review, tag and import, so nothing lands unseen.
| Record | What comes from WFX | Where it lands in AIMS360 |
|---|---|---|
| Vendors | Supplier name, address and contact details created in WFX | The AIMS360 vendor list, ready for vendor purchase orders. Address lines are capped at 40 characters, with an optional auto trim. |
| Styles | Article code, article name, size card, division, season and selling price, plus the primary style image and primary color image | A style master with colors and sizes. Body code, fabric content and country of origin sit at style level in AIMS360. |
| Materials | Fabrics and trims linked to the styles, or marked new or updated in WFX | AIMS360 materials, created automatically 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 land on the trims tab, which is the tab that holds color and size detail, and labor lands on the labor tab. |
| Importer costing | Supplier cost, freight, duty, other cost, wholesale price and retail price from the WFX cost sheet | The importer costing tab on the style, with FOB and sell price able to vary by color |
Do the mappings once, before the first import. Division, season and size scale mappings are required.
In AIMS360, open the WFX setup screen under Modules and enter the credentials WFX issued you. Choose to download new and updated records.
WFX has two style grouping fields. The recommended mapping is WFX product group to the AIMS360 body code and WFX product sub-category to the AIMS360 style group. You can reverse it, but the choice cannot be undone after you save, so agree it first.
Required. Pick the AIMS360 division for each WFX division. Several WFX divisions can point at one AIMS360 division.
Required. Create the WFX season codes in AIMS360, then map each one to the matching AIMS360 season.
Required. Match each WFX size card to the closest AIMS360 size scale and each WFX size name to an AIMS360 size. AIMS360 holds up to 23 sizes per scale.
To bring labor costs across, enter each WFX labor code exactly as WFX has it and map it to an AIMS360 manufacturing operation.
Material imports create a missing vendor by default. Importer costing is switched on with an AIMS360 specialist, because WFX cost sheets are named differently from brand to brand.
Validate the settings, save, then import a few vendors and one finished style end to end before you bring in a season.
The BOM refers to all three, so it goes last. Rows that fail validation stay in the pending view with a reason, and most fixes can be made on the import screen itself.
Download new data, tag the vendors you want and import. A five character vendor code is required, and the validation log tells you which rows need fixing before they will go.
Only styles at the Production stage in WFX come across, and color and size are mandatory. Unit of measure has to match an AIMS360 code: assorted, case, dozen, each or gross.
New materials are created on import. A WFX color code longer than five characters will not import as it stands, so those rows wait in pending until the code is fixed.
Import last, after vendors, styles and materials exist. A BOM can be labor only, and you can change the BOM in WFX and re-import it to update the style in AIMS360.
For brands buying fully packaged goods. You choose new and updated records, to keep managing prices in WFX, or new records only, to manage them in AIMS360 after the first import. Manufactured costing in AIMS360 is covered on the bill of materials page.
| WFX cost sheet | AIMS360 importer costing | Level |
|---|---|---|
| Supplier cost | FOB | Can differ by color |
| Wholesale price | Sell price | Can differ by color |
| Freight charge | Sea or air freight | Style |
| Duty % | Duty % | Style |
| Other cost | Other | Style |
| Retail price | Suggested retail price, shown on the style master | Style |
AIMS360 codes are shorter and stricter than WFX codes. Agree a naming convention with your WFX team before styles are built, not after.
| Field | What AIMS360 expects |
|---|---|
| Vendor code | 5 characters, letters and numbers only. Vendor name up to 40, address lines up to 40. |
| Color code | 2 to 5 characters, letters and numbers only. Color name up to 20. |
| Material code | 2 to 6 characters, letters and numbers only. Material name up to 40. |
| Style number | 3 to 15 characters. The hyphen is the only special character allowed. Style name up to 50. |
| Size card | Attach it when the style is created in WFX, so the sizes populate. A card added later can leave the style without sizes, and it will not import. |
After the import, AIMS360 is the system the sellable style lives in. Keeping a second working copy anywhere else is how 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. |
| Product record | The article as it is developed | The style master 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, and the cost margin reports run on |
| Production and selling | Nothing | Vendor POs, cut tickets, work in process, receiving, orders, allocation, invoicing |
Stated up front so they do not surface in the middle of a season.
| Point | Detail |
|---|---|
| One way only | WFX sends to AIMS360. AIMS360 does not send styles, stock or orders back to WFX. |
| Deletes do not carry | Deleting a material in WFX does not delete or cancel it in AIMS360. Retire it in AIMS360 yourself. |
| Fabric tab stays empty | WFX sends fabric by color and size, so fabric lines sit on the trims tab. Cost totals and material reports still add up. |
| Labor is per color | Labor arrives per color, and any size detail on a WFX labor line is ignored, because AIMS360 does not carry labor by size. |
| Labor needs its own section | The WFX BOM section must be named Labor, exactly, or labor costs will not import. |
| Existing data needs Automap | Records you exported from AIMS360 into WFX still come back as new on the first import. Run Automap so they link instead of duplicating. |
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.
To worldfashionexchange.com. This page is AIMS360's and covers the integration. AIMS360 does not host WFX or sign you into it, and questions about WFX software belong with the WFX team.
One way, from WFX into AIMS360. Nothing is sent from AIMS360 back to WFX, so inventory, orders and production status stay in AIMS360.
When its product 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.
Yes. Fabric, trim and labor lines import against the style by color and size. Import styles, materials and vendors first, then the BOM. Fabrics and trims land on the trims tab and labor on the labor tab.
Yes. Change the BOM in WFX, adding, editing or removing items, and re-import it. The same import screen updates the style BOM in AIMS360. Check it after import, as you would any BOM.
Yes. A BOM with labor costs and no fabric or trim lines imports. Labor needs its WFX section named Labor and the labor codes mapped to AIMS360 manufacturing operations first.
Yes, through importer costing, which an AIMS360 specialist switches on with you. Supplier cost becomes FOB and wholesale price becomes sell price, both per color. Freight, duty, other cost and retail price come across per style.
Not if you use Automap. Export your existing styles, colors, materials and vendors to WFX, then run Automap in the import screens so incoming WFX records link to the ones you already have.
Vendor code 5 characters, color code 2 to 5, material code 2 to 6, style number 3 to 15 with the hyphen as the only special character. Code fields take letters and numbers only. Names have length limits too.
If you map a WFX size card to an AIMS360 scale with more sizes, the sizes the style does not come in are marked inactive on that style. The scale text can still show them on some forms.
No. Tech packs, sampling and vendor comments stay in WFX. AIMS360 runs what comes after: vendor purchase orders, cut tickets, work in process, receiving, orders and invoicing.
WFX, BeProduct and Centric PLM. WFX is the one with its own import modules inside AIMS360, documented record by record.
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.