What to look for in fashion operations software: a buyer’s guide for Shopify brands
Eight questions to ask in every demo — from size grids and techpacks to which data syncs with Shopify in which direction — and what a good answer sounds like.
· 7 min read
In short: Good fashion operations software models sizes and colours as one product, starts before the SKU with techpacks and approvals, buys by size from real demand, says exactly which data syncs with Shopify in which direction, ships and processes returns without a second app, and publishes a price you can plan around.
Fashion operations software runs the work between a design and a delivered order: product development, purchasing from factories, stock by size and location, Shopify orders, shipping and returns. Most clothing brands assemble it from four or five tools. The questions below are the ones that separate software built for fashion from general inventory software that happens to allow variants.
1. Does it treat sizes and colours as one product?
A jacket in three colourways and five sizes is 15 variants. Ask whether the system generates them from a size chart and colourways, or whether each one is a separate product code that you link by naming convention. Then ask whether purchase orders, stock and sales reports can be read as a size grid. If the answer is "export it to a spreadsheet", the software does not think in sizes.
2. Does it start before the SKU exists?
Most of a fashion product's data is created during development: sketches, measurements, construction, materials, costing and fit comments. Ask whether the system holds a techpack, versions it, and turns the approved style into the sellable product without re-entering it. If development lives in another tool, every approved style is typed in twice.
See how this works in practice in fashion PLM: styles, techpacks and lifecycles.
3. Does it buy by size from real demand?
The hard part of restocking apparel is the size split, not the total. Ask how the system calculates sales velocity: a good answer counts only the days each size was in stock, so a sold-out medium does not look like a slow medium. Then ask whether that size curve pre-fills the next purchase order.
See demand planning and markdowns by size.
4. What exactly syncs with Shopify, and in which direction?
"Two-way Shopify sync" means little on its own. Ask the vendor to name each kind of data and its direction: products, variants, images, prices, stock, orders, fulfilments, refunds, returns and customers. Stock is commonly pushed one way, from the operations system to Shopify, so the system of record is unambiguous. Also ask whether you can edit, cancel and refund orders from the system, or only read them.
5. Can it ship and process returns without another app?
Ask whether labels are bought inside the system on your own carrier accounts, whether customs data travels from the product to the label, and whether packing is verified by scanning. For returns, ask whether refunds and restocking happen in one flow and land in Shopify.
See order fulfilment for Shopify fashion brands and scan-to-pack verification.
6. Does it price each market, duties included?
If you sell abroad, ask whether the system keeps a price list per market and can fold duty and import tax into the price (delivered duty paid), using an HS code stored on each product. Without that, international customers pay again at the door.
See Shopify Markets, DDP and HS codes.
7. How is it priced?
Check three things: whether the price is per user or flat, whether modules you need are add-ons, and whether there is a one-off onboarding fee. Per-user pricing grows with every hire; add-on modules can double a quote. A published price is a good sign.
8. What should it not try to be?
Fashion operations software does not need to be your accounting system or schedule a factory floor you do not own. If you manufacture in-house, you need an MRP for that job. If you work with external factories, development, buying, stock and fulfilment around production matter more than scheduling inside it.
A checklist for your next demo
| Question | A good answer |
|---|---|
| Sizes and colours | Generated from a size chart; readable as a grid |
| Product development | Versioned techpack; approved style becomes the product |
| Buying | In-stock sales velocity; size-curve purchase orders |
| Shopify | Each data type and its direction named, in writing |
| Shipping | Labels on your own carrier accounts; scan-verified packing |
| Returns | Refund, store credit and restock in one flow |
| International | Price per market; duties included; HS codes per product |
| Pricing | Published; modules not sold separately; no onboarding fee |
KNKTD OS was built to answer yes to these questions for Shopify fashion brands that work with external factories. See KNKTD OS pricing, or compare the options in the best inventory and operations software for Shopify fashion brands.
Frequently asked questions
What is fashion operations software?
Software that runs the work between a design and a delivered order for a clothing brand: product development and techpacks, purchasing from factories, stock by size and location, Shopify orders, shipping and returns. It replaces the four or five separate tools most brands assemble.
What features should fashion operations software have?
Sizes and colours generated as one product, versioned techpacks that become the sellable product, purchasing by size from in-stock sales velocity, a named list of what syncs with Shopify in which direction, labels on your own carrier accounts, returns with refunds and restock in one flow, prices per market with duties included, and a published price.
Do I need an MRP or ERP as a fashion brand?
Only if you manufacture in-house, in which case an MRP schedules your floor. Brands that work with external factories need development, buying, stock and fulfilment around production more than scheduling inside it, and usually keep accounting in a dedicated accounting tool.