ChatGPT answers, unedited

For a small fashion line with custom tags and recurring production runs, I’d choose based on whether you need just ecommerce + SKU tracking or actual production/MRP management.

My recommendation: Shopify + Cin7 Core

shopify.com is the best customer-facing ecommerce platform for your situation, while cin7.com is the stronger system for inventory and production as your operation gets more complicated.

• Shopify — storefront, checkout, orders, product variants, SKUs, barcodes, customer data and basic purchasing. Shopify supports inventory at the variant level and purchase orders, so it's perfectly capable of getting a small line off the ground. Shopify Shopify App Store
• Cin7 Core — production runs, bills of materials, raw materials, finished goods, purchasing, batch tracking and production planning. It specifically supports apparel size grids, per-size barcodes and ecommerce variant syncing. Cin7 Cin7

That combination becomes particularly useful if, for example, you have:

Style: T-shirt 001
→ Black / S
→ Black / M
→ Black / L
→ Cream / S
→ Cream / M
→ Cream / L

…and each finished garment requires:

1 garment + 1 custom woven label + 1 hangtag + 1 polybag + 1 care label

Cin7 can model those materials through a bill of materials, track the components consumed during production, and keep raw-material, work-in-progress and finished-goods inventory connected. Cin7 Cin7

When I'd not add Cin7 yet

If you're launching with, say, 5–20 styles and a handful of production runs, and your manufacturer is handling most of the manufacturing logistics, I'd start with Shopify alone. Keep your production BOMs and run quantities in a simple spreadsheet initially.

Then add Cin7 when you start having problems such as:

• "How many labels do I actually have left?"
• "Which production run did these units come from?"
• "How much fabric/trim do I need to reorder?"
• "What's currently in production versus finished?"
• "Why does Shopify say I have 80 units when only 35 are actually available?"
• Multiple manufacturers or warehouses
• Wholesale + DTC inventory needing to stay synchronized

Cin7 is explicitly designed around raw materials → production → finished goods and supports production scheduling, component tracking and batch/lot traceability. Cin7 Cin7

What I'd choose at different stages

One important point: don't design your SKU system around the custom tag. The garment/style/size/color should generally determine the sellable SKU; your custom label, hangtag, care label, packaging, etc. should be components/materials in your production system. That keeps your ecommerce catalog clean while still letting you know exactly what goes into each production run.

If you tell me roughly how many styles, colors/sizes, units per production run, and whether you're manufacturing yourself or using a factory, I can tell you whether Cin7 is worth paying for at launch or whether Shopify alone will be enough.

• "How many labels do I actually have left?"
• "Which production run did these units come from?"
• "How much fabric/trim do I need to reorder?"
• "What's currently in production versus finished?"
• "Why does Shopify say I have 80 units when only 35 are actually available?"
• Multiple manufacturers or warehouses
• Wholesale + DTC inventory needing to stay synchronized

Cin7 is explicitly designed around raw materials → production → finished goods and supports production scheduling, component tracking and batch/lot traceability.

What I'd choose at different stages

For a small fashion label with custom tags and recurring production runs, I’d avoid choosing an ecommerce platform based on storefront features alone. Your key question is: where will you manage the relationship between finished-garment SKUs, materials, production batches, and sales?

My recommendation: Shopify + Katana

I’d start with shopify.com for ecommerce and katanamrp.com for inventory/production.

That gives you a relatively lightweight setup without jumping straight into a full ERP.

Shopify handles the customer-facing side

Shopify is particularly good for fashion because each garment can have variants such as:

• Style: JKT-01
• Color: BLK
• Size: S
• Final SKU: JKT-01-BLK-S

Shopify tracks inventory at the variant level and supports separate inventory by location. Shopify App Store Shopify

So your website, orders, payments, returns, and sellable SKU inventory live there.

Katana handles the production side

This is where I think your use case gets interesting.

Katana can track materials → production → finished goods, including Bills of Materials, manufacturing orders, production operations, scheduling, and inventory movements. Katana Katana

For example, you could structure a garment roughly like:

Then a production run can consume your fabric/labels/packaging and create 150 finished garments.

The Shopify integration can sync orders and inventory between the two systems, and Katana can use Shopify SKUs to match products. Katana Katana

Why I wouldn't use Shopify alone

Shopify is perfectly capable of managing your finished-goods SKUs, but production gets more awkward when you need to answer questions like:

"I have enough fabric for 80 more jackets, but only 45 custom labels. How many jackets can I actually produce?"

Or:

"I ordered 300 labels for this style. How many have been consumed by production run #2?"

That's where a manufacturing/inventory system becomes valuable.

When I'd choose something else

If you're extremely small — say 5–20 styles, very small production runs, and you're outsourcing manufacturing entirely — you could start with Shopify alone + spreadsheets. Don't buy an ERP before you need one.

If you're going to have substantial wholesale, multiple warehouses, 3PLs, or lots of channels, I'd investigate a more comprehensive apparel ERP such as Uphance or Cin7. Apparel-specific ERP becomes more compelling as wholesale, EDI, marketplaces, and complex inventory enter the picture. Uphance

If you're manufacturing significant quantities yourself, Katana becomes much more compelling because its manufacturing workflows are specifically designed around materials, production orders, scheduling, and finished-goods inventory. Katana

What I'd do in your position

I'd build the system like this:

Shopify → sales/orders
↓
Katana → SKUs + materials + BOMs + production runs
↓
Fabric / labels / trims / packaging → finished garments
↓
Finished inventory → Shopify

And I'd establish your SKU convention before launching. That's much harder to fix after you've accumulated hundreds of orders.

If you tell me roughly how many styles you're launching, typical production-run size, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can tell you whether I'd choose Shopify alone, Shopify + Katana, or an apparel ERP for your specific operation.

For a small fashion label with custom tags and recurring production runs, I’d separate the decision into two layers:

1. E-commerce storefront: where customers buy.
2. Inventory/production system: where you manage SKUs, materials, production batches, and finished goods.

My pick: Shopify + Cin7

Shopify is the easiest storefront choice, while Cin7 is the stronger choice for production/inventory once you need more than basic stock counts.

Shopify handles apparel variants very naturally—e.g. Style × Color × Size, with a unique SKU for each combination. It also supports bulk SKU editing/import and variant-level inventory. help.shopify.comhelp.shopify.com

Cin7 becomes valuable when you need to say things like:

"I’m producing 150 units of Style 001, using 75 yards of fabric, 150 custom neck labels and 150 hangtags, and I need to know what's currently in production versus finished."

It supports BOMs, raw materials, work-in-progress, production runs, component tracking, purchasing, and finished-goods inventory, while integrating with Shopify. www.cin7.com It specifically markets its system to fashion/apparel companies. www.cin7.com

How I'd structure your system

For example:

Then a production run could consume:

RUN-001 → 50 × JKT001-BLK-S + 75 × JKT001-BLK-M + 50 × JKT001-BLK-L

while deducting the appropriate fabric, labels, tags, buttons, packaging, etc.

That's much better than treating every SKU as simply "50 in stock."

What I'd choose at your stage

If you're launching with perhaps 10–50 styles and relatively simple manufacturing:
Shopify alone initially can be perfectly reasonable. Keep your production-run spreadsheet alongside it until the operational complexity justifies another system.

If you're already working with a factory and need to track materials → production → finished inventory:
Shopify + Cin7 is my recommendation. Cin7 has the manufacturing functionality Shopify isn't designed to provide, including BOMs and production planning. www.cin7.com

If your main requirement is just SKUs, sizes/colors, and sales inventory:
Don't overbuy software. Shopify's native variant/SKU system is likely enough initially. help.shopify.comhelp.shopify.com

One important thing about your custom tags

I'd make custom labels/tags separate inventory items, rather than embedding them into the finished SKU.

For example:

TEE001-WHT-M = finished garment
LBL-TEE001 = woven neck label
TAG-TEE001 = hangtag

Then your production/BOM says that one finished garment consumes one of each. That gives you visibility into whether you're short on garments, labels, or tags before a production run.

If you tell me roughly how many styles/SKUs you're launching, whether you're manufacturing domestically or overseas, and whether the factory or you are buying the labels/tags, I can narrow this down to the best 2–3 systems and tell you which one I'd actually use.

For a small fashion label, I’d separate “ecommerce storefront” from “inventory/production system.” Your custom tags, size/color variants, and production runs make the latter unusually important.

My top choice: Shopify + Cin7 Core

shopify.com for the customer-facing store, paired with cin7.com for inventory and production.

Why I like this setup for apparel:

• SKUs: You can structure every garment as variants by style, color, and size—for example JKT01-BLK-S.
• Production runs: Cin7 supports bills of materials, production jobs, purchasing, and manufacturing workflows. Cin7 Cin7
• Apparel-specific inventory: Cin7 supports size grids, per-size barcodes, and ecommerce variant synchronization. Cin7
• Small-batch manufacturing: You can track raw materials → production → finished garments rather than simply treating each SKU as something you bought wholesale.
• Contract manufacturers: Cin7 Core supports outsourced/contract manufacturing, which is particularly useful if your factory produces your runs. Cin7
• Shopify integration: Inventory and orders can sync between the two systems. Cin7

When I'd not use Cin7 yet

If you're launching with, say, 5–15 styles, a handful of sizes/colors, one manufacturer, and relatively small production runs, Cin7 may be more operational software than you need on day one.

In that case, I'd start with Shopify alone, establish a disciplined SKU system, and add a dedicated inventory/MRP system once production gets complicated.

The key is to design your SKU architecture correctly from the beginning.

For example:

Then separately track the components:

• Main fabric
• Lining
• Zippers
• Buttons
• Woven neck label
• Care label
• Hangtag
• Packaging

That distinction becomes really valuable: SKU = what you sell; production run = when/how you made it; BOM = what went into making it.

One important consideration for your custom tags

I'd actually make labels/tags inventory items, rather than thinking of them as part of the ecommerce product listing.

So a production run might consume:

100 jackets → 100 neck labels → 100 care labels → 100 hangtags

That lets you see when you're short on labels even though you technically have enough fabric and garments to fulfill the run.

Cin7 specifically supports BOM/material tracking and production workflows, making it considerably better suited to this kind of operation than a basic ecommerce platform. Cin7 Cin7

My recommendation by stage

Very early / validating the brand:
Shopify → keep production tracking in a simple spreadsheet initially.

Growing small label / multiple production runs:
Shopify + Cin7 Core → my recommendation for you.

More complex manufacturing, multiple factories, wholesale, multiple warehouses:
Move toward a more comprehensive ERP/MRP setup. Cin7 Core can scale into this territory; its higher tiers add more advanced manufacturing and planning capabilities. Cin7

If you tell me roughly how many styles/SKUs you're launching, your expected first production quantity, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can recommend the simplest setup that won't become a nightmare when you hit your second or third collection.

For a small fashion label, I’d choose Shopify + a lightweight manufacturing/inventory system, rather than trying to make one ecommerce platform do everything.

My pick: Shopify + Craftybase

Shopify is the best storefront foundation for you: it handles product variants/SKUs, orders, inventory, barcodes, purchasing, and multi-location stock. apps.shopify.com

Then add Craftybase for the production side. It is particularly well suited to small-batch apparel: you can track fabric, trims, labels, components, finished garments, production batches, and true production costs. craftybase.com

The workflow I'd use is:

Shopify
→ customer-facing products & variants
→ SKU/barcode
→ orders & payments

Craftybase
→ bill of materials for each garment
→ materials/components inventory
→ production runs/batches
→ labor/material costs
→ finished-goods inventory
→ sync available stock back to Shopify craftybase.com

For example, you could have:

JKT-001-BLK-S = black jacket, small
JKT-001-BLK-M = black jacket, medium

Then the production recipe can say each jacket requires 1 shell + 1 lining + 6 buttons + 1 custom woven label, and a production run of 50 jackets consumes those materials and creates 50 finished units.

When I'd choose Katana instead

Katana is the stronger choice if you're expecting the operation to become more manufacturing-heavy—multiple production locations, contractors, warehouse processes, purchasing, barcode scanning, forecasting, etc. Its Shopify integration is designed specifically to make Katana the inventory/production hub while Shopify remains the storefront. support.katanamrp.com

Simple decision

For your description, I'd start with Shopify + Craftybase. It gives you a relatively simple ecommerce setup without losing the ability to answer the questions that matter to a fashion brand: How many units of each size/color do I actually have? What materials went into this run? What did this batch cost me? And when should I produce the next 50?

If you tell me roughly how many styles/SKUs you're launching, whether production is in-house or outsourced, and whether your custom tags are just labels or need their own inventory/SKUs, I can narrow this down to the best setup and workflow for your line.

For a small fashion label, I’d separate the question into two parts: e-commerce (selling) and production/inventory (making and tracking). If you expect multiple production runs, custom labels/tags, sizes/colors, and eventually wholesale, my top choice would be:

My recommendation: Shopify + Cin7 Core

Shopify is excellent as the storefront and sales system. It handles size/color variants and lets you assign a unique SKU to every variant—e.g. JKT01-BLK-S. help.shopify.comhelp.shopify.com

Then use Cin7 Core as your inventory/production layer once your manufacturing gets beyond simple spreadsheets. Cin7 supports BOMs, production orders/runs, component inventory, batch tracking, contract manufacturing, and production costing. help.core.cin7.com

For fashion, that's particularly useful because you can model something like:

Style → Color → Size → SKU → Production Run

For example:

• DRS01-BLK-S
• DRS01-BLK-M
• DRS01-BLK-L
• Production Run #001 → 50 units
• Production Run #002 → 100 units

You can also track the components going into a production run, rather than merely counting finished garments. Cin7 supports mapping component batches to finished-product batches. help.core.cin7.com

But don't overbuild on day one

If you're launching with, say, 5–20 styles, a few colors/sizes, and one or two factories, I'd actually start with Shopify alone + a disciplined SKU/production spreadsheet. Shopify already gives you per-variant SKUs, inventory management, bulk editing/import, and multi-location inventory. help.shopify.comhelp.shopify.com

Move to Cin7 when you're struggling with things like:

• tracking fabric/trims/labels separately from finished garments
• multiple production runs of the same style
• purchase orders to factories
• work-in-progress
• landed/manufacturing costs
• wholesale + DTC inventory simultaneously
• knowing exactly which materials went into a particular production run

Cin7 is specifically designed to connect raw materials, WIP and finished goods and can handle contract manufacturing. www.cin7.com

One important distinction about your custom tags

If by custom tags you mean physical woven labels/hangtags sewn or attached to the garment, I would not make the tag number your primary SKU.

I'd structure it more like:

BRAND-STYLE-COLOR-SIZE

Then separately track:

• garment SKU
• hangtag SKU
• woven-label SKU
• fabric SKU
• trim/component SKUs
• factory/production-run ID

That gives you much more flexibility if you change your branding or tag supplier without changing the identity of the garment.

Bottom line:
Very small launch → Shopify + spreadsheet.
Serious small label with repeat production → Shopify + Cin7 Core.
Complex manufacturing from the beginning → Cin7 Core deserves to be the operational backbone, with Shopify as the storefront.

If you tell me roughly how many styles you’re launching, number of colors/sizes, whether you're manufacturing domestically or overseas, and whether you plan to sell wholesale, I can recommend the exact setup—including a SKU naming system and production-run structure that won't become a mess as the brand grows.

For a small fashion label, I’d choose based on how much production control you need, not just which platform has the nicest storefront.

My pick: Shopify + a production/inventory app

Shopify is probably the best starting point if you’re launching small and selling primarily DTC. It handles individual SKUs/variants, multi-location inventory, purchase orders, transfers, and incoming stock. www.shopify.com

For example, you could structure:

Jacket → Black → Small → SKU JKT-BLK-S

and separately track your custom woven label, hangtag, packaging, etc. Then use an inventory/production app when you outgrow Shopify's native tools.

Why I'd pick it for you: easy storefront + strong SKU management + lots of room to add specialized production tools later. You don't have to build your entire operational system before you've proven the collection.

If production runs are the core challenge: Odoo

Odoo is much more compelling if you're actually manufacturing collections, rather than simply selling finished garments.

Odoo can give each size/color combination its own SKU and inventory, while its manufacturing system handles bills of materials, manufacturing orders, work centers, production planning, subcontracting, and lot/serial tracking. www.odoo.com

It can also use a single bill of materials across multiple garment variants and specify which components apply to particular variants. www.odoo.com

That becomes useful for something like:

Tee / Black / M
Fabric: 1.2 yd
Woven neck label: 1
Hangtag: 1
Packaging: 1
Production run: 50 units

How I'd decide

One important distinction: custom tags don't necessarily require special ecommerce software. I'd model the tag as a production component rather than as a customer-facing SKU. Your finished garment gets the sellable SKU; the label/hangtag gets its own internal component SKU if you need to reorder and track those materials.

For a first collection, I'd lean Shopify unless you're already coordinating substantial manufacturing. It will let you launch quickly without turning your business into an ERP implementation project.

If you tell me roughly how many styles × colors × sizes you're launching, whether you're manufacturing yourself or using a factory, and your approximate production run size, I can recommend a specific setup (including how I'd structure your SKUs, BOMs, and production runs).

For a small fashion label with custom woven/printed tags, multiple sizes/colors, and repeat production runs, I’d separate the problem into two layers:

My recommendation: Shopify + Cin7 Core

Shopify as your customer-facing ecommerce platform, with Cin7 Core handling the operational side.

That combination is particularly strong once you need more than a spreadsheet can comfortably handle:

• SKUs & variants: style → color → size can be maintained as individual inventory items. Cin7 specifically supports apparel size grids, per-size barcodes, and ecommerce variants. www.cin7.comwww.cin7.com
• Production runs: you can create production orders and track components/raw materials against finished goods. Its manufacturing tools support BOMs, production planning, and outsourced/contract manufacturing. www.cin7.com
• Custom tags: I'd treat your branded neck tags, care labels, hangtags, packaging, etc. as components/material SKUs, rather than trying to manage them solely inside Shopify.
• Inventory synchronization: Shopify orders flow into Cin7 and inventory can sync back, so a sale of a size/color reduces the operational inventory accordingly. help.core.cin7.com
• Small-batch production: you can model something like DRESS-01 / BLACK / M as the finished SKU, with a BOM containing fabric + label + care tag + other components. A 100-unit production run then consumes those inputs and creates 100 finished units.

The important caveat

I wouldn't start with Cin7 just because it's powerful. It's considerably more operational software than a new designer may need. Cin7 Core currently starts at $349/month through its Shopify App Store listing, before potential add-ons. apps.shopify.com

If you're launching with, say, 10–30 styles, a few colorways, and relatively simple production, I'd start with Shopify and add a lighter inventory/production workflow rather than building an ERP around the business immediately.

If you're already planning multiple factories, production runs, purchase orders for fabric/trims, wholesale + DTC, or detailed COGS, I'd go straight to Shopify + Cin7.

How I'd structure your SKU system

For fashion, don't make the SKU describe everything about the garment. Give each sellable variant a stable identifier, e.g.:

JKT001-BLK-S
JKT001-BLK-M
JKT001-CRM-S

Then separately track:

• Style: JKT001
• Color: BLK
• Size: M
• Season/collection: FW26
• Production run: PR-001, PR-002, etc.
• Fabric lot
• Label/tag version
• Factory/vendor
• Cost

That distinction becomes extremely useful when you reorder the same style but change the label or produce it at a different factory.

Bottom line: for a genuinely small launch, Shopify first; for a label where production and inventory complexity are central to the business, Shopify + Cin7 Core is the setup I'd choose. Cin7 explicitly positions its apparel system around sourcing, production, inventory, and ecommerce synchronization. www.cin7.comwww.cin7.com

If you tell me roughly how many styles/SKUs you're launching, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can narrow this down to the 2–3 best setups for your particular workflow.

For a small fashion label, I’d separate the question into “what runs my storefront?” and “what runs my production?” Those aren’t always best handled by the same system.

My recommendation: Shopify + Cin7 Core

Shopify is the strongest choice for your customer-facing ecommerce store, while Cin7 Core is the better fit for the operational side if you expect meaningful production complexity.

Cin7 Core can handle SKUs, size/color variants, BOMs, raw materials, purchase orders, production/assembly, batch tracking, and finished goods. It also supports contract manufacturing, which is particularly relevant if you're sending cut-and-sew work to an outside factory. www.cin7.comwww.cin7.com

For fashion specifically, I'd structure your system roughly like:

Style → color → size → SKU

For example:

JKT-01-BLK-S
JKT-01-BLK-M
JKT-01-BLK-L

Then separately track the components:

• Fabric
• Lining
• Zippers/buttons
• Woven neck label
• Care label
• Hangtag
• Packaging
• Finished garment

A production run can then consume those components and create finished inventory. Cin7's BOM and production functionality is designed for exactly this sort of component-to-finished-product workflow. www.cin7.com

When I'd choose something simpler

If you're launching with, say, 5–20 styles, a handful of colors/sizes, and relatively straightforward factory runs, I'd start with Shopify and avoid introducing a heavy ERP immediately. You can add a dedicated inventory/manufacturing system once spreadsheets start becoming painful.

If you're already coordinating multiple factories, fabrics, trims, production batches, reorders, wholesale orders, and several hundred SKUs, I'd implement Cin7 Core from the beginning. Its size-grid/variant support, barcode capabilities, BOMs and manufacturing tools are much better suited to that environment. www.cin7.com

The key thing I'd look for in your case isn't just “SKU management.” Make sure the software can distinguish a product SKU from a production run. You want to be able to answer:

“I have 240 units of this SKU in stock. 120 came from production run #001 and 120 from #002, and run #002 used a different fabric supplier/cost.”

That becomes extremely valuable as your label grows.

If you tell me roughly how many styles/SKUs you're launching, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale as well as DTC, I can narrow this down to 2–3 systems and tell you which I'd pick.

For a small fashion label, I’d separate the decision into ecommerce vs. production/inventory management. If you want one system to eventually handle both, Cin7 Core + Shopify is the combination I’d look at first.

My recommendation

1. Shopify — best customer-facing ecommerce platform

Shopify

Shopify is excellent for selling the collection and managing SKU-level inventory. Each size/color combination can have its own variant, SKU, price, and inventory quantity. Shopify currently supports up to 100 variants per product. apps.shopify.comwww.cin7.com

For example:

• JKT-001-BLK-S
• JKT-001-BLK-M
• JKT-001-BLK-L
• JKT-001-RED-S

Your custom sewn-in tag doesn't need to be the SKU itself. I'd make the SKU an internal, consistent identifier and print the SKU/barcode on your hangtag or packaging label.

2. Cin7 Core — best if production runs are a major part of your workflow

Cin7 Core

This is where I'd look if you're having garments manufactured in batches. Cin7 can manage raw materials → production → finished garments, including bills of materials, production jobs, component inventory, and production costs. It also supports apparel-specific size grids and per-size barcodes. www.cin7.com

So you could have something like:

Style: Oversized Linen Jacket
SKU: OLJ-001-BLK-M
Production run: RUN-2026-08-01
Fabric: 2.1 yd/run
Labels: 1/run
Buttons: 6/run
Units produced: 75
Units QC-passed: 72
Units available: 72

Cin7 can also connect production demand to Shopify, so you're not manually reconciling ecommerce inventory with manufacturing inventory. www.cin7.com

What I'd choose at your stage

The important distinction is that Shopify is primarily optimized around selling finished products, whereas Cin7 is designed to track the underlying manufacturing process—raw materials, WIP, finished goods, BOMs, production scheduling, and production costs. www.cin7.com

One thing I'd do before buying anything

Design your SKU architecture first. For fashion, I'd generally structure it as:

STYLE – COLOR – SIZE – [optional revision]

For example:

DRS-004-CRM-XS
DRS-004-CRM-S
DRS-004-CRM-M

Then keep production-run IDs separate from SKUs:

RUN-004-01 = first production run
RUN-004-02 = second production run

That distinction becomes extremely useful when you reorder the same style six months later, change the factory, alter the fabric, or discover a problem with one particular production batch.

Bottom line: If you're genuinely launching small and want to keep overhead low, start with Shopify, but establish a professional SKU system from day one. If you're already planning recurring production runs with factories, BOMs, fabric/trims, and custom labeling, I'd build around Shopify + Cin7 Core rather than trying to force Shopify to become your manufacturing system. www.cin7.com

If you tell me roughly how many styles/SKUs you're launching, whether production is domestic or overseas, and whether you're manufacturing yourself or using a factory, I can narrow this down to the best 2–3 setups for your specific workflow.

For a small fashion label, I’d choose Shopify as the ecommerce platform, and—if you’re actually managing production runs rather than just finished inventory—pair it with Katana.

My pick: Shopify + Katana

Shopify should be your customer-facing system. It handles product variants, SKUs, inventory, orders, purchasing, and multiple sales channels. Its current Basic plan starts at $29/month when billed annually ($39 monthly). www.shopify.com

Katana becomes your production/inventory layer. Its Shopify integration can sync orders and inventory while giving you production planning and fulfillment control. support.katanamrp.com

That combination makes particular sense for apparel because you can structure something like:

Style: JKT-001
Color: Black
Size: M
SKU: JKT-001-BLK-M
Production run: SS26-001
Units produced: 50
Label/tag version: V2

Then you can distinguish what you sell from how you manufacture it—which becomes important when you have the same garment produced in multiple runs, with different tags, trims, fabrics, or suppliers.

When I'd consider Cin7 instead

If you're already dealing with multiple suppliers, substantial raw-material inventory, contract manufacturers, or complicated production runs, look at Cin7 Core. It has BOMs, batch tracking, manufacturing, purchasing, size grids/barcodes, and support for contract manufacturing. Cin7 specifically markets its system for fashion/apparel. www.cin7.com

It's more powerful, but I'd consider it too much operational software for many very small labels starting out.

One important point: don't make your production-run number part of the customer-facing SKU unless you have a specific reason. I'd keep the SKU stable for the sellable variant and track the production/batch/run separately. That way, if you make 100 black medium jackets now and another 100 six months later, you don't have to create a completely new sellable product.

If you tell me roughly how many styles/SKUs you're launching, whether you're manufacturing yourself or using a factory, and whether your custom tags are unique per collection/run, I can recommend the simplest setup—and show you exactly how I'd structure your SKUs, variants, BOMs, and production runs.

For a small fashion label with custom tags, multiple sizes/colors, and limited production runs, I’d avoid choosing an ecommerce platform based on storefront features alone. You need two things:

1. Ecommerce: sell each size/color as a distinct SKU and keep inventory accurate.
2. Production/inventory: know how many units are planned, in production, finished, and allocated to orders.

My recommendation: Shopify + Katana

Shopify is the best starting point for the storefront, while Katana handles the production side.

Katana can import your Shopify products and create the SKU mapping, then you can define materials, bills of materials (BOMs), and production operations. Shopify orders can flow into Katana, while inventory and fulfillment status sync back. support.katanamrp.com

A typical setup could look like:

Shopify

• T-shirt / Black / Small → TS-BLK-S
• T-shirt / Black / Medium → TS-BLK-M
• T-shirt / Cream / Small → TS-CRM-S

Katana

• Fabric
• Custom woven neck tag
• Care label
• Thread
• Packaging
• Cut/sew production
• Finished garment

Then a production run of, say, 50 black medium T-shirts can consume the appropriate materials and turn them into 50 finished units rather than you manually adjusting a spreadsheet.

When I'd choose Cin7 instead

Cin7 Core is worth considering if you expect the operation to become more complicated fairly quickly—for example, wholesale + DTC, multiple warehouses, contract manufacturers, lots of SKUs, or detailed batch/production tracking.

Cin7 specifically supports size grids and per-size barcodes, production jobs with contract manufacturers, BOMs, batch tracking, and more advanced manufacturing/capacity planning. www.cin7.com It also integrates with Shopify and keeps SKUs, variants, orders, and inventory synchronized. www.cin7.com

How I'd choose

For your specific description, I'd start with Shopify + Katana. It's a good balance: Shopify handles the customer-facing brand experience, while Katana gives you the production/inventory layer you don't want to outgrow immediately.

One important design decision: make every sellable size/color combination its own SKU from day one. Your custom tags don't necessarily need separate sellable SKUs, but they should exist as production components/materials so you know how many tags to order for each run.

If you tell me roughly how many styles/SKUs you expect, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can narrow this down to the best setup and explain how I'd structure your SKU + production-run system.

For a small fashion line with custom tags, SKU tracking, and production runs, I’d avoid choosing a platform based only on the storefront. Apparel gets complicated quickly because you need to track:

• style → color → size variants
• raw materials and trims (fabric, labels, buttons, packaging)
• purchase orders with factories
• production batches/runs
• samples vs production units
• landed costs
• inventory by location
• wholesale + direct-to-consumer sales

www.shopify.com

A good shortlist:

Best starting point for most small fashion brands: Shopify + an apparel inventory/ERP add-on

Best if: you’re launching DTC, doing limited drops, and want a polished brand storefront.

Pros:

• Excellent for fashion ecommerce and product variants
• Easy SKU management
• Huge ecosystem for inventory, purchase orders, forecasting, and manufacturing integrations
• Works well for pop-ups and retail selling later

Cons:

• Shopify itself is not a full production management system; you may outgrow native inventory tools once you have many factories, wholesale accounts, or complex production schedules. www.uphance.comecommercewebsitecreate.com

Common setup:

• Shopify = storefront + orders
• Apparel ERP/inventory tool = production + purchasing + deeper inventory control

Best if production runs are a major part of your workflow: apparel ERP software

For a designer brand making seasonal collections, small-batch runs, or working with manufacturers, consider fashion-specific systems such as:

• ApparelMagic — built around apparel operations, including product development, inventory, manufacturing, and orders. www.softwareadvice.com
• Uphance — focuses on apparel product lifecycle management, production, inventory, and order workflows. apps.shopify.com

These are better when you need things like:

• tech packs
• bills of materials (BOMs)
• production status tracking
• factory purchase orders
• wholesale order management

If you’re very early (first collection, <100 SKUs)

You can often start simpler:

• Shopify for ecommerce
• a lightweight inventory tool
• accounting software
• spreadsheets for production calendars

Just make sure every garment has a consistent SKU system from day one.

Example SKU structure:

STYLE-COLOR-SIZE

Example:
JKT-OLV-M

• JKT = jacket style
• OLV = olive color
• M = medium

Then separate:

• finished goods SKU
• fabric/material SKU
• packaging SKU
• sample SKU

My recommendation by stage

For a small designer label launching its first line, I’d usually start with Shopify as the commerce backbone and add an apparel ERP only when production tracking becomes painful. That keeps costs and complexity down while preserving a path to scale. www.uphance.comecommercewebsitecreate.com

A few details would change the recommendation:

1. How many styles/SKUs will your first drop have?
2. Are you manufacturing yourself, using a cut-and-sew factory, or print-on-demand?
3. Will you sell wholesale to boutiques, or only direct online?

For a small fashion label with custom tags and relatively limited production runs, I’d start with Shopify rather than jumping straight into a full manufacturing ERP.

My recommendation

1. Shopify — best starting point

Shopify is a particularly good fit if your priority is selling online + keeping SKUs organized without creating a huge operational system.

• You can give every size/color combination its own SKU—for example DRS-01-BLK-S. Shopify specifically recommends unique SKUs for every variant. help.shopify.comhelp.shopify.com
• Inventory is tracked at the variant level, which works well for apparel sizing and colors. help.shopify.comhelp.shopify.com
• You can create supplier purchase orders and track incoming inventory. help.shopify.com
• You can bulk-edit/import SKUs, useful when you're setting up an entire collection. help.shopify.com
• If your custom woven labels, hangtags, packaging, etc. are treated as components, you can eventually add an inventory/manufacturing app rather than replacing your storefront.

The limitation: Shopify itself isn't really a production-run/MRP system. It won't give you the same depth of BOMs, raw-material consumption, work orders, and manufacturing scheduling that a dedicated production system does.

2. Cin7 + Shopify — best if production management is central

I'd consider this if you're already thinking in terms of:

Collection → styles → sizes/colors → fabric/trims → production run → finished inventory → Shopify sale

Cin7 can manage SKUs, size grids, per-size barcodes, BOMs, production jobs, raw materials, WIP and finished goods. It also supports contract manufacturing, which could be useful if you're working with an outside cut-and-sew factory. www.cin7.com

It integrates with Shopify, so Shopify can remain your customer-facing store while Cin7 becomes the operational/inventory system. www.cin7.com

The downside is cost and complexity. Cin7's production capabilities are considerably more than most very small labels need at launch. www.cin7.com

What I'd do in your position

If you're launching with, say, 5–20 styles and a few hundred pieces per production run, I'd choose:

Shopify → now
Shopify + manufacturing/inventory app → as production gets complicated
Cin7 + Shopify → once you're regularly managing multiple factories, materials, production runs, wholesale, or multiple sales channels

The important thing is to design your SKU structure correctly from day one, because your custom tags, purchase orders, production records and ecommerce inventory should all ultimately reference the same SKU.

For example:

Then I'd keep production-run information separate from the SKU. So TEE01-BLK-M remains the permanent SKU, while something like RUN-2026-01 identifies the particular manufacturing batch. That makes it much easier to reorder the same garment without creating a new SKU.

One important distinction: if by “custom tags” you mean custom garment labels/hangtags, rather than merely product tags in the ecommerce platform, tell me that. I can recommend a setup specifically for fashion production—SKUs + BOMs + fabric/trims + labels + factory POs + production runs + Shopify and tell you which software I'd pick at your size.

For a small fashion label, I’d avoid choosing an ecommerce platform based on storefront features alone. Your SKU structure, size/color variants, BOMs, production batches, and inventory movements are what will determine whether the system still works once you have multiple styles and production runs.

My pick: Shopify + Katana

Shopify for the storefront, paired with Katana for inventory and production.

That combination is particularly well suited to an emerging clothing brand:

• Shopify: website, checkout, customer orders, product variants, discounts, etc.
• Katana: raw materials, finished goods, BOMs, purchase orders, production scheduling, manufacturing orders and inventory.
• Shopify and Katana sync orders and inventory, with Katana acting as the production/inventory hub. support.katanamrp.com
• Katana supports both make-to-order and make-to-stock manufacturing orders, which maps nicely to fashion production runs. support.katanamrp.com
• You can track barcodes for receiving, production and finished retail products. support.katanamrp.com

How I'd structure your clothing SKUs

For example, suppose you launch:

Oversized Linen Shirt

• OLS-BLK-XS
• OLS-BLK-S
• OLS-BLK-M
• OLS-BLK-L
• OLS-WHT-XS
• etc.

Then Katana can have the underlying production recipe/BOM:

OLS-BLK-M
→ linen fabric: 1.65 yd
→ buttons: 7
→ sewing labels: 1
→ neck label: 1
→ hang tag: 1
→ packaging: 1

A production run of 100 shirts then consumes those materials and creates finished inventory. That's much more useful for you than simply telling Shopify "100 shirts exist."

Shopify itself recommends unique SKUs for every variant and supports bulk SKU editing/imports. help.shopify.com

Two alternatives worth considering

Cin7 Core + Shopify — I'd choose this if you expect the operation to become more sophisticated relatively quickly. Cin7 has strong inventory, purchasing, BOM, manufacturing and size-grid capabilities; it specifically supports size variations and per-size barcodes. www.cin7.com

Shopify alone — perfectly reasonable if you're doing very small runs initially and your manufacturer handles most of the production accounting. Shopify is good at selling and tracking finished SKUs, but I'd start looking at an MRP/inventory system once you're juggling fabric/component inventory and multiple production runs.

My decision rule

One important point about your custom tags: I'd make your garment label, hang tag, packaging, etc. actual production components in the BOM rather than treating them as marketing supplies. That way, when you make 250 units of a style, the system knows you're consuming 250 neck labels and 250 hang tags along with the fabric and buttons.

If you tell me (1) roughly how many styles/SKUs you'll launch with, (2) whether you're manufacturing yourself or using a factory, and (3) whether you'll sell wholesale as well as DTC, I can recommend the exact setup and SKU/production-run structure I'd use for your brand.