Approved styles in Centric PLM are created in AIMS360 automatically, with colorways, sizes, BOM, materials, costing, suppliers and images. AIMS360 sends material inventory back to Centric. Custom integration built and supported by AIMS360.
Centric PLM is where your team designs, develops and approves the style. AIMS360 is where it gets bought, made, stocked, sold and invoiced. This integration connects the two at the moment that matters: when a style is approved in Centric, its style header, colorways, size range, bill of materials, materials, costing, suppliers and images are created in AIMS360 automatically. AIMS360 sends material inventory back, so developers in Centric see what fabric and trim is actually on hand.
Yes. AIMS360 has a custom integration with Centric PLM, built and supported by AIMS360 and running in production. When a style is approved in Centric, the sync fires automatically and creates the style header, colorways, size range, bill of materials, material records, costing, supplier records and images in AIMS360. It is two-way for one object: AIMS360 sends material inventory back to Centric. Sales orders, purchase orders, shipments and invoices stay in AIMS360. Centric Software, the company behind Centric PLM, is a Dassault Systèmes subsidiary that reports more than 2,900 customers in over 65 countries.
If you are weighing PLM options rather than connecting one you already run, start with the fashion PLM integrations overview, which covers Centric, WFX and BeProduct side by side.
Eight objects. Each one becomes a real AIMS360 record, which is why a purchase order to the factory can be raised the same day the style is approved.
| Object | From Centric PLM | Becomes in AIMS360 | What it unlocks |
|---|---|---|---|
| Style header | The approved style | A style record with style number, name, division, body and season | Sales orders, purchase orders, line sheets |
| Colorways | Each colorway on the style | A color on the style, using your AIMS360 color codes | Style, color, size inventory |
| Size range | The style's size range | The style attached to an AIMS360 size scale | Size-level stock, prepacks, retailer EDI |
| Bill of materials | The BOM | BOM lines, each pointing at an AIMS360 material record | Material requirements, raw material purchase orders |
| Materials | Fabrics, trims and components | Material records in raw material and trim inventory | Receiving, on-hand quantities, inventory back to Centric |
| Costing | The cost sheet | Cost values on the style | Landed cost and margin |
| Suppliers | Factory and material suppliers | Vendor records | Vendor purchase orders, production tracking |
| Images | Style images | Images on the style record | Line sheets, the B2B portal, the spec sheet |
Tech packs are not on that list on purpose. They are authored in Centric and stored in AIMS360 as files against the style, order or cut ticket. AIMS360 generates a spec sheet from the style record, with measurements, BOM, construction and images, but it does not author tech packs.
| Step | What happens | Who does it |
|---|---|---|
| 1. Style approved in Centric | A developer moves the style to its approved status in Centric PLM. That status change is the trigger. Nobody exports a file or runs an import. | Your product team, in Centric |
| 2. Mapping applied | The integration translates Centric attributes into AIMS360 codes: division, body, size scale, color codes, material codes and vendor codes, using the mapping agreed at setup. | The integration, automatically |
| 3. Records created | Vendors and materials are created first, then the style with its colorways, size scale, BOM lines, costing and images, so every BOM line points at a material record that exists. | The integration, automatically |
| 4. Buy and make | A vendor purchase order goes to the factory from the AIMS360 style and BOM. Production tracking follows the cut ticket through the operations you define. | Your production team, in AIMS360 |
| 5. Materials received | Fabric and trim are received against the material records Centric sent, so raw material and trim inventory reflects what is physically in the warehouse. | Your warehouse, in AIMS360 |
| 6. Material inventory back to Centric | AIMS360 sends on-hand material quantities to Centric, so the next style is specced around fabric that actually exists. | The integration, automatically |
From step 4 onward the style behaves like any other AIMS360 style: it allocates, picks, ships on retailer EDI, sells on Shopify and the B2B portal, and invoices from one stock record.
Material inventory, and only material inventory, today. AIMS360 sends on-hand fabric and trim quantities to Centric so a developer specifying a new style can see what is already in the warehouse. Sales orders, purchase orders, shipments, invoices and finished goods inventory stay in AIMS360 and are not sent to Centric.
Every brand carries fabric and trim it bought for a style that sold less than planned. When Centric shows the developer that 1,400 yards of a cotton twill are already on hand, the next style can be built around it instead of a fresh minimum order.
Order, shipment and invoice data belong to the systems that act on them: the ERP, the warehouse and the books. Pushing them into a PLM creates a second copy nobody reconciles. Centric gets the one thing its users decide with, which is material availability.
Both hold a style. The difference is which version. Centric holds it while it is changing. AIMS360 holds it once it is a product.
Centric Software lists fashion and apparel, outdoor and sports, home and furniture, and cosmetics and personal care among the industries it serves. AIMS360 runs the ERP side for the same categories, which is why the pairing comes up: see fashion and apparel, footwear, outdoor and sporting goods and cosmetics and personal care.
The mapping is done once, with the AIMS360 team, and it is where almost all of the setup effort goes. Centric attribute names do not have to match AIMS360 names. They have to translate cleanly.
| Mapped once | Why it matters |
|---|---|
| Divisions and bodies | Centric categories become AIMS360 divisions and body codes, which drive reporting and line sheets. |
| Size scales | Each Centric size range is matched to an AIMS360 size scale so the style can be stocked and sold by size from day one. |
| Color library | Centric colorways map to AIMS360 color codes. Shared colors across styles reuse the same code. |
| Material library | Centric materials map to AIMS360 material codes. This is also the key that lets material inventory travel back. |
| Supplier list | Centric suppliers map to AIMS360 vendor codes, so purchase orders address the right factory or mill. |
AIMS360 code fields have length rules, and the Centric side is checked against them during mapping rather than at sync time.
| AIMS360 field | Rule |
|---|---|
| Style number | 3 to 15 characters, alphanumeric. The hyphen is the only special character allowed. Style name up to 50 characters. |
| Color code | 2 to 5 characters, alphanumeric. Color name up to 20 characters. |
| Material code | 2 to 6 characters, alphanumeric. Material name up to 40 characters. |
| Vendor code | 5 characters, alphanumeric. Vendor name and address lines up to 40 characters. |
| Constraint | Detail |
|---|---|
| Only material inventory goes back | Orders, shipments, invoices and finished goods inventory are not sent to Centric. Material on-hand quantities are. |
| No design tools in the ERP | AIMS360 does not sketch, render 3D or author tech packs. Tech packs stay in Centric and are stored in AIMS360 as files. |
| Revisions after approval | The sync is built around the approval event. How a style changed after approval is handled is agreed at scoping, because some brands want every revision re-pushed and some want the ERP style locked once purchase orders exist. |
| Custom, not a marketplace toggle | The connection is scoped and configured with the AIMS360 team against your Centric instance and your mapping. Support for the connector comes from AIMS360. |
| Codes have rules | Style, color, material and vendor codes outside the AIMS360 length and character rules are fixed in the mapping, not on the fly. |
Yes. AIMS360 has a custom integration with Centric PLM, built and supported by AIMS360 and running in production. When a style is approved in Centric, its style header, colorways, size range, bill of materials, materials, costing, suppliers and images are created in AIMS360 automatically, and AIMS360 sends material inventory back to Centric. It sits alongside the WFX and BeProduct connectors on the fashion PLM integrations page.
The style reaching its approved status in Centric PLM. That status change fires the sync automatically. Nobody exports a file or runs an import, and styles that are still in development do not reach the ERP, so AIMS360 is not filled with styles that never get made.
Eight objects: the style header with style number, name, division, body and season; each colorway as a color on the style; the size range attached to an AIMS360 size scale; bill of materials lines pointing at AIMS360 material records; the material records themselves; cost sheet values; factory and material suppliers as AIMS360 vendors; and style images.
Yes, for one object. AIMS360 sends material inventory back to Centric PLM so developers see on-hand fabric and trim quantities inside the PLM. Everything else flows from Centric into AIMS360. Sales orders, purchase orders, shipments, invoices and finished goods inventory stay in AIMS360 and are not sent to Centric.
Because material availability is the one operational fact a developer decides with. When Centric shows that a fabric is already on hand in the AIMS360 warehouse, the next style can be built around it instead of a fresh minimum order, and leftover fabric from a slow style gets used rather than written off. The quantities come from raw material and trim inventory in AIMS360.
Live. It is running in production for AIMS360 customers on Centric PLM. Ask during a demo and we will walk through an approved style crossing into AIMS360.
AIMS360 built it and AIMS360 supports it, with the same 24/7 support team that handles the rest of the platform. It is a custom integration configured against your Centric instance and your mapping, not a marketplace app you switch on. Centric Software, the company behind Centric PLM, is a Dassault Systèmes subsidiary.
Divisions and bodies, size scales, the color library, the material library and the supplier list. Each is mapped once during setup so Centric attributes translate into AIMS360 codes. AIMS360 code fields have length rules: style numbers 3 to 15 characters with the hyphen the only special character allowed, color codes 2 to 5, material codes 2 to 6 and vendor codes 5, all alphanumeric. Centric naming conventions are checked against those during mapping.
That is agreed during scoping rather than assumed, because the right answer differs by brand. Some want every post-approval change re-pushed into AIMS360. Others want the ERP style locked once purchase orders exist, with changes handled deliberately. Raise it before go-live so the behavior matches how your production team works. How implementation is run covers where that conversation happens.
No. Tech packs are authored in Centric PLM and stored in AIMS360 as files against the style, order or cut ticket. AIMS360 generates a spec sheet from the style record, covering measurements, bill of materials, construction and images, which is the document that travels with the purchase order and cut ticket.
It depends on what your product team does all day. AIMS360 carries styles and colors, size scales, BOMs, materials, costing and production tracking natively, and many brands run product development there. Centric earns its place when several designers work the same line at once, tech packs need version history a factory can be held to, sample and fit rounds need comments, or suppliers need a portal. If that is your daily reality, keep Centric and let AIMS360 take the style at approval.
The categories both systems already serve. Centric Software lists fashion and apparel, outdoor and sports, home and furniture, and cosmetics and personal care among its industries. AIMS360 runs the ERP side for those and more, including footwear, jewelry and accessories, wellness and supplements, baby and children's and pet products. See the industries AIMS360 serves.
Approve a style in Centric, then open it in AIMS360 with its colorways, sizes, BOM, cost sheet and suppliers already there. That is the whole demo, and it takes less time than re-keying one style by hand.
