ChatGPT answers, unedited

For a small clothing line, I’d separate the storefront from the inventory/production system rather than trying to make one platform do everything.

My shortlist

What I'd choose for your situation

Shopify + Katana would be my starting point if you're producing relatively small batches.

Shopify handles your customer-facing store, product variants, checkout, etc., while Katana handles the operational side. Its Shopify integration is specifically designed to bring orders into production planning, keep inventory synchronized, and reflect fulfillment status. Katana

That becomes particularly useful for fashion because you might have something like:

• JKT-001-BLK-S
• JKT-001-BLK-M
• JKT-001-BLK-L
• JKT-001-CREAM-S
• etc.

You can then track the components/materials that go into each garment and the resulting finished inventory, rather than maintaining a giant spreadsheet for every production run.

When I'd pick Cin7 Core instead

I'd go with Shopify + Cin7 Core if you already know you'll have multiple suppliers, wholesale accounts, several sales channels, or increasingly complicated production/inventory.

Cin7 Core supports product families with size/color variants, each with its own SKU, and has BOM/assembly manufacturing, purchase orders, inventory locations, and manufacturing functionality. Cin7 Core Cin7

It also has a direct Shopify integration where orders and inventory can flow between the systems. Cin7 Core

Cin7 explicitly positions its system for fashion/apparel and supports sourcing, production, inventory, warehousing, and multiple ecommerce channels. Cin7

One important distinction for your custom tags

If by custom tags you mean woven neck labels/hangtags with your brand and SKU/barcode, I'd structure your system around style → color → size → production batch, rather than making each production run a completely new SKU.

For example:

Style: Oversized Tee
Style code: TEE-001

Then:

• TEE-001-BLK-S
• TEE-001-BLK-M
• TEE-001-BLK-L
• TEE-001-WHT-S
• TEE-001-WHT-M

And separately track:

• Production run: RUN-2026-09-01
• Quantity produced
• Factory/supplier
• Fabric lot
• Production cost
• Date received
• QC status

That gives you stable SKUs while still letting you know which batch produced the garments you're holding.

Bottom line: If you're launching small and want to keep the tech stack manageable, I'd start with Shopify + Katana. If you expect the operational side of the brand to become substantial—wholesale, multiple warehouses/channels, lots of materials and production complexity—I'd look at Shopify + Cin7 Core instead. Katana Cin7

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 a specific setup and SKU/production-run structure.

For example:

Style: Oversized Tee
Style code: TEE-001

Then:

• TEE-001-BLK-S
• TEE-001-BLK-M
• TEE-001-BLK-L
• TEE-001-WHT-S
• TEE-001-WHT-M

And separately track:

• Production run: RUN-2026-09-01
• Quantity produced
• Factory/supplier
• Fabric lot
• Production cost
• Date received
• QC status

That gives you stable SKUs while still letting you know which batch produced the garments you're holding.

Bottom line: If you're launching small and want to keep the tech stack manageable, I'd start with Shopify + Katana. If you expect the operational side of the brand to become substantial—wholesale, multiple warehouses/channels, lots of materials and production complexity—I'd look at Shopify + Cin7 Core instead.

For a small fashion label, I’d separate “storefront” from “production/inventory system.” Your custom tags and production runs make SKU structure and manufacturing tracking more important than simply having a pretty online store.

My shortlist

My recommendation: start with Shopify if you're launching a relatively small collection, but structure your SKUs properly from day one. Shopify can be your customer-facing store, while a dedicated inventory/production layer can be added as your manufacturing gets more complicated.

If you're already dealing with cut-and-sew production, multiple factories, fabric/trims, BOMs, production batches, and work-in-progress, I'd seriously consider Cin7 Core + Shopify from the outset. Cin7 supports size grids, per-size barcodes, ecommerce variants, purchase orders, bills of materials, production, and contract manufacturing. Cin7 Cin7

Why I'd lean Cin7 for your particular use case

Imagine you have:

Jacket — Black — Medium

You may actually need to track:

• Finished-garment SKU
• Size/color variant
• Fabric lot
• Labels/tags
• Zippers/buttons/trims
• Factory
• Production run
• Quantity ordered
• Quantity completed
• WIP
• Finished inventory
• Cost per unit

That's where ordinary ecommerce inventory starts becoming inadequate. Cin7 is designed to track raw materials, WIP and finished goods, and its manufacturing functionality supports BOMs and production scheduling. Cin7 Cin7

Your custom tags are actually important

I'd design your SKU system before choosing the software.

For example:

JKT-01-BLK-S

JKT-01-BLK-M

JKT-01-BLK-L

Then keep production run/batch information separate from the SKU:

• SKU: JKT-01-BLK-M
• Production run: RUN-2026-001
• Quantity: 75
• Factory: Factory A
• Label version: LBL-03
• Cost: $XX
• Production date: September 2026

That way, if you reorder the same jacket six months later, the SKU doesn't change just because it's a new production run.

For apparel specifically, Lightspeed also treats each size/color combination as its own SKU, while Squarespace supports individual SKUs for variants such as size and color. Lightspeed Retail Squarespace Help

What I'd choose at different stages

If you're launching 5–20 styles:
Shopify. Keep it simple and use an inventory/manufacturing app only when necessary.

If you're launching with a real production operation:
Shopify + Cin7 Core. This gives you the polished ecommerce storefront plus a much more serious inventory/production backbone. Cin7 specifically integrates with Shopify and other ecommerce channels. Cin7

If the website itself is the priority and production is extremely simple:
Squarespace Commerce. It supports unlimited SKUs and multidimensional variants, so it's perfectly capable of a small clothing catalog. Squarespace

If you expect boutiques/wholesale + your own physical shop:
I'd look harder at Cin7 or Lightspeed, because inventory across multiple channels becomes increasingly important.

If you tell me roughly how many styles you're launching, how many sizes/colors per style, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can map out the exact SKU + production-run structure I'd use for your brand.

What I'd choose at different stages

If you're launching 5–20 styles:
Shopify. Keep it simple and use an inventory/manufacturing app only when necessary.

For a small fashion label, I’d avoid trying to make the ecommerce platform do everything. Your key distinction is:

• Ecommerce: selling online, customer orders, payments, product pages.
• Inventory/production: SKU variants, fabric/trims, BOMs, production runs, work-in-progress, supplier POs, finished goods.

My pick: Shopify + Katana

shopify.com + katanamrp.com is probably the best fit if you're launching small but expect to manufacture multiple styles, colors and sizes.

Shopify handles the customer-facing store and orders. Katana can act as your inventory/production hub, syncing Shopify orders and inventory while managing manufacturing, locations, barcodes, purchasing and production planning. Katana Katana

For example, you could structure a style like:

JACKET-01-BLK-S
JACKET-01-BLK-M
JACKET-01-BLK-L

Then separately track the components:

• Outer fabric
• Lining
• Zipper
• Woven neck label
• Hang tag
• Care label
• Packaging

Your production run can consume those materials and create finished-goods inventory. That's much closer to how a clothing business actually operates than simply treating every size/color as an isolated Shopify product.

The alternatives

cin7.com is particularly strong for apparel: it supports size grids, per-size barcodes, ecommerce variants, BOMs, assembly manufacturing, batch tracking and production planning. It also supports contract manufacturing, which could be useful if your garments are made by an outside factory. Cin7 Cin7 Cin7

Cin7 is the one I'd consider if you're already thinking about multiple production runs, wholesale, several suppliers, or multiple sales channels. It integrates with Shopify and other ecommerce channels and is designed to track raw materials, WIP and finished goods. Cin7 Cin7

One important thing: design your SKU system first

For fashion, I'd make your SKU encode style + color + size, rather than putting production information into the SKU.

For example:

Product: Oversized Cotton Shirt
Style: SH01
Color: BLK
Size: M
SKU: SH01-BLK-M

Then give each production run its own batch/production-run identifier, e.g. RUN-2026-01.

That lets you distinguish:

SH01-BLK-M = the sellable SKU
RUN-2026-01 = the manufacturing run that produced 80 units

This becomes extremely useful when you reorder the same style six months later, change factories, change a label, or need to figure out which run a particular batch came from.

What I'd do in your position

Start with Shopify + Katana if you're launching with perhaps a handful of styles and dozens of variants and want something manageable.

I'd move toward Cin7 Core when the operation starts looking more like a proper apparel company—multiple factories, wholesale accounts, larger purchase orders, several warehouses, complex BOMs, or substantial production planning.

If you tell me roughly how many styles × colors × sizes you're launching, whether you're manufacturing yourself or using a factory, and whether you're selling wholesale as well as DTC, I can recommend the exact setup and SKU/production-run structure I'd use.

For a small fashion label with custom tags, size/color variants, and limited production runs, I’d separate the problem into two layers:

• Ecommerce: where customers shop and orders come in.
• Inventory/production: where you track SKUs, materials, production quantities, and finished goods.

My pick: Shopify + Katana

shopify.com + katanamrp.com is probably the best fit if you're starting small but expect the line to become more operationally complex.

Shopify handles the customer-facing store, product variants, orders, payments, etc. Katana becomes the production/inventory brain. Its Shopify integration can match products by SKU, synchronize inventory, and handle bills of materials, materials, and production operations. Katana Katana

For example, you could structure a garment like:

Style: LUNA-01
Variant SKUs: LUNA-01-BLK-S, LUNA-01-BLK-M, LUNA-01-CRM-S, etc.
BOM: shell fabric + lining + zipper + label + hangtag
Production run: 50 units
Run: 20 S / 20 M / 10 L
Custom tag: label version A
Supplier: Factory X

That distinction becomes really useful when you have the same garment produced in multiple runs. You can see what materials are required, what has been produced, and what is actually available for sale rather than treating everything as one giant inventory number.

When I'd choose Cin7 instead

cin7.com is worth considering if you're already anticipating wholesale, multiple warehouses, lots of SKUs, or more sophisticated inventory operations.

Cin7 is particularly fashion-friendly: it explicitly supports apparel inventory, sourcing/production, warehouses, purchasing, and multichannel selling. Its Shopify integration also maps SKUs, variants, locations and stock between the systems. Cin7 Cin7 Core

The downside for a very small label is that it can be more ERP/inventory system than you need initially.

What I would not do

I wouldn't start with Shopify alone if you're actually manufacturing garments.

Shopify is excellent as your storefront, but once you're dealing with:

• fabric/raw-material inventory
• cut/sew production
• production batches
• components/BOMs
• multiple production runs
• supplier POs
• finished vs. committed inventory
• different SKU variants

you'll eventually want a dedicated inventory/production layer.

My recommendation by stage

For your particular use case, I'd start with Shopify + Katana. It gives you a relatively clean setup without forcing you into a heavyweight ERP before you've established the line.

One important design decision: make your SKU system independent of your product tags. Your SKU should identify the actual sellable variant; your sewn-in label/hangtag should be treated as a component or attribute. That will save you a lot of headaches when you change your branding without changing the garment itself.

The downside for a very small label is that it can be more ERP/inventory system than you need initially.

What I would not do

I wouldn't start with Shopify alone if you're actually manufacturing garments.

Shopify is excellent as your storefront, but once you're dealing with:

For a small fashion label with custom tags, size/color variants, and limited production runs, I’d avoid choosing a basic ecommerce platform based on storefront features alone. You want something that can handle SKUs + BOMs/materials + production batches + finished-goods inventory.

My recommendation: Shopify + Katana

shopify.com for your storefront, paired with katanamrp.com for inventory and production.

Why I like this setup for a young clothing brand:

• Shopify handles the customer-facing store, orders, payments, and product variants.
• Katana handles the operational side: materials, BOMs, manufacturing orders, production operations, purchasing, and inventory. It supports batch/lot tracking and can track outsourced production as well. Katana Katana
• Katana's manufacturing workflow lets you track a production order through individual operations, which is useful when a garment goes through cutting → sewing → finishing → tagging → completed inventory. Katana
• Its current Core plan starts at $299/month, with unlimited SKUs, so I'd consider it once your production complexity justifies the cost. Katana

If production management is your #1 priority: Cin7 Core

cin7.com is probably the stronger all-in-one operations system.

It specifically supports fashion/apparel, including size grids, per-size barcodes, ecommerce variants, BOMs, batch tracking, purchase orders, and manufacturing. Cin7 Cin7

That's particularly attractive for something like:

Jacket → Black → Medium → SKU JKT-BLK-M → 50 units → Production Run #003 → custom woven label + hangtag + zipper + fabric

Cin7 can track the materials/components through production and into finished goods, rather than treating the garment simply as an ecommerce SKU. Cin7

How I'd choose

One important point: don't make your custom tags/hangtags part of the finished-product SKU. Treat them as components/materials in the BOM. That way, if you order 500 woven labels for a style and produce 150 garments now and 200 later, your system can tell you how many labels/materials remain and what each production run consumed.

If you tell me roughly (1) how many styles, (2) number of sizes/colors, (3) whether you're manufacturing yourself or using a factory, and (4) your monthly software budget, I can narrow this down to the best 2–3 systems for your specific label.

For a small fashion line with custom tags, size/color variants, and limited production runs, I’d avoid choosing an ecommerce platform based on storefront features alone. Your key question is: where will the “source of truth” for SKUs, materials, production quantities, and finished inventory live?

My recommendation: Shopify + Cin7 Core

Shopify is the best storefront/ecommerce layer for your situation, while Cin7 Core is worth adding once production gets complicated.

Shopify handles apparel variants cleanly—e.g. JACKET-001-BLK-S, JACKET-001-BLK-M, etc.—and each variant can have its own SKU and inventory. Shopify Help Center Shopify Help Center

Cin7 is the more interesting piece for production: it supports BOMs, raw materials, production/assembly, purchasing, batch tracking, and inventory across raw materials → WIP → finished garments. It also integrates with Shopify. Cin7 Cin7

For example, you could structure a garment like:

• Style: JKT-001
• Variant: JKT-001-BLK-M
• BOM: shell fabric + lining + zipper + thread + woven label + hangtag
• Production run: JKT-001-RUN-01
• Quantity: 50 units
• Status: Cutting → Sewing → Finishing → QC → Finished
• Finished inventory: 50 units, subsequently reduced as Shopify orders come in

That becomes particularly valuable when you're doing small batches rather than continuously manufacturing the same item. Cin7 supports BOM/component tracking and production planning, and its documentation specifically covers outsourced/contract manufacturing as well. Cin7 Cin7

What I'd choose at different stages

I wouldn't start with a giant ERP unless you're already dealing with substantial manufacturing complexity. For a new label, the overhead can outweigh the benefit.

One important thing: design your SKU system first

Before importing anything into Shopify, I'd establish a SKU convention that won't collapse when your collection grows. Shopify itself recommends planning SKU formats around attributes such as brand/style/size and keeping every variant unique. Shopify Help Center

For fashion, I'd use something like:

STYLE-COLOR-SIZE

Example:

DRS-003-BLK-XS
DRS-003-BLK-S
DRS-003-BLK-M

Keep production-run numbers separate from the SKU. Your SKU identifies what the garment is; the production run identifies when/how many you made.

That distinction becomes extremely useful if you make:

• 30 units in September
• 50 units in November
• 100 units next spring

They're still the same sellable SKU, but you can track each manufacturing batch independently.

Bottom line: I'd launch on Shopify, establish a disciplined SKU/variant structure from day one, and add Cin7 Core when you need BOMs, raw-material tracking, production runs, purchase orders, and manufacturing visibility. Cin7's current Core offering includes SKU management, purchase orders, BOM tracking and standard assembly manufacturing, with more advanced production capabilities available as an add-on. Cin7 Cin7

If you tell me roughly how many styles you plan to launch, your typical run size (e.g. 20/50/100 units), and whether you're manufacturing yourself or using a factory, I can recommend the simplest setup and show you exactly how I'd structure your SKUs, BOMs, tags, and production runs.

For fashion, I'd use something like:

STYLE-COLOR-SIZE

Example:

DRS-003-BLK-XS
DRS-003-BLK-S
DRS-003-BLK-M

For a small fashion line with custom tags, limited production runs, and growing SKU complexity, I’d avoid choosing a platform based only on “online store” features. Your bigger challenge will be managing:

• style → color → size variants
• SKU creation and barcodes
• production batches / cut-and-sew runs
• materials and components (fabric, labels, trims)
• purchase orders to manufacturers
• inventory arriving in waves
• preorders and limited drops

Apparel has unusual inventory needs because a single style can explode into dozens of SKUs (for example, one jacket × 5 sizes × 4 colors). Apparel-focused systems often handle this style/color/size structure better than generic ecommerce tools. AIMS360 ERP Research

My shortlist for a small clothing brand

1. shopify.com + an inventory/production app — best starting point for most indie labels

Best if: You are primarily DTC (selling through your own website, Instagram, pop-ups, etc.)

Pros:

• Excellent storefront and checkout
• Strong variant/SKU support
• Huge ecosystem for barcode, inventory, preorder, and fulfillment apps
• Easy to scale from 20 SKUs to thousands

Cons:

• Shopify alone is not a production management system
• You’ll likely add tools for purchase orders, manufacturing, or materials tracking

A common setup:

• Shopify → ecommerce
• Inventory app → stock control
• Accounting software → finances
• Spreadsheet/PLM tool → production calendar and tech packs

For many emerging designers, this is the least painful path. Shopify

2. ApparelMagic — best if production management matters now

Best if: You are already doing seasonal collections, working with factories, or selling wholesale.

Strengths:

• Built around apparel workflows
• Handles style/color/size matrices
• Supports inventory, orders, production, and wholesale operations

This is closer to an apparel ERP than a simple ecommerce platform. AIMS360

3. Uphance — good middle ground for growing fashion brands

Best if: You want something fashion-specific but not enterprise-heavy.

Useful for:

• product development
• inventory
• purchase orders
• production tracking
• wholesale workflows

It is aimed more at brands that are moving beyond spreadsheets but are not ready for a large ERP. The Retail Exec

4. Katana — good if you manufacture yourself or run small batches

Best if: You personally manage production, assembly, or small manufacturing runs.

Good for:

• bills of materials
• work orders
• raw materials
• production status

Less ideal for fashion-specific size/color workflows at scale. AIMS360

5. AIMS360 — later-stage option

Best if: You grow into wholesale, retailers, EDI, and more complex operations.

Powerful, but probably more system than a brand needs at launch. Apparel-native ERP systems are generally designed for brands with more operational complexity. AIMS360 G2

What I would choose based on your stage

Before you commit, test these five things in a demo

Ask the vendor to show you:

1. Create one garment style

• 3 colors
• 6 sizes
• custom SKU codes
• barcode labels
• Create a production run

• 200 units ordered from a factory
• expected delivery date
• partial shipment
• Track components

• fabric
• custom woven labels
• hang tags
• packaging
• Handle a preorder

• sell before inventory arrives
• reserve units from a production batch
• See profitability

• true cost per unit including tags, trims, labor, and shipping

For a new designer launching a small line, I would usually start with Shopify as the storefront and add apparel operations tools only when production complexity demands it. Moving into a full apparel ERP too early can create more admin work than it saves. Shopify AIMS360

If you tell me your expected launch size (e.g., 50 SKUs vs 500 SKUs, handmade vs factory-made, DTC only vs wholesale), I can narrow this to a specific stack.

What I would choose based on your stage

For a small fashion label, I’d separate “storefront” from “production/inventory system.” Your custom tags and production runs make manufacturing workflow more important than just having a nice online store.

My pick: Shopify + Cin7 Core

Shopify is the storefront I’d choose, paired with Cin7 once your production becomes more than you can comfortably manage in spreadsheets.

• Shopify handles your customer-facing store, product variants, SKUs, orders and basic purchasing. Its purchase orders can identify variants by SKU/barcode and record supplier SKU, cost and quantities. Shopify Help Center
• Cin7 Core is the stronger piece for your production side: BOMs, raw materials, work-in-progress, finished goods, production jobs, purchasing and inventory. It specifically supports apparel, including size grids and per-size barcodes. Cin7 Cin7
• Cin7 can connect with Shopify, so you can have one SKU/inventory system feeding your online store rather than manually reconciling sales and production. Cin7

How I'd structure your SKUs

For example, suppose you make a black cropped jacket:

JKT-CRP-BLK-S
JKT-CRP-BLK-M
JKT-CRP-BLK-L

Then your production/BOM can track things such as:

• Outer fabric
• Lining
• Zippers
• Buttons
• Custom woven neck label
• Size label
• Hangtag
• Packaging

A production run of 100 jackets can then consume those materials and create 100 finished units, while Shopify sells the individual size/color variants.

That's much better than treating "Black Jacket" as a single inventory item.

What I'd choose at different stages

Cin7 is particularly compelling once you're managing raw materials → production run → finished garments → ecommerce inventory. It supports BOMs, production scheduling, material tracking and purchasing rather than merely counting finished products. Cin7 Cin7

One caution: I wouldn't start with a heavyweight ERP just because you're a fashion company. If you're launching with, say, 10–30 styles and a few hundred units, Shopify plus a disciplined SKU/BOM spreadsheet may be enough initially. Add Cin7 when production complexity actually warrants it.

shopify.com · cin7.com

If you tell me roughly how many styles/SKUs you expect, whether you're manufacturing yourself or using a cut-and-sew factory, and your approximate first production run, I can recommend the simplest setup that won't force you to migrate everything six months from now.

For a small fashion label with custom tags and limited production runs, I’d avoid choosing an ecommerce platform based only on storefront features. Your key requirement is the ability to treat style + color + size + production run + materials as distinct inventory data.

My recommendation: Shopify + Katana

shopify.com + katanamrp.com is probably the best starting point if you’re launching small.

• Shopify handles your storefront, checkout, customer orders and product variants.
• Katana can act as the production/inventory layer. Its Shopify integration sends orders into Katana for production planning and fulfillment while keeping inventory synchronized. Katana Katana
• You can structure SKUs around something like JKT-BLK-M and keep the ecommerce variant separate from your internal production information.
• For each production run, you can track the materials and quantities needed rather than simply treating "100 jackets" as one inventory number.
• This setup lets you start relatively lean and add manufacturing sophistication as your line grows.

When I'd choose Cin7 instead

If you're already expecting multiple collections, lots of SKUs, contract manufacturers, wholesale accounts, or more complicated production, I'd seriously consider cin7.com.

Cin7 is considerably more operations-oriented: it supports product SKUs, size grids and per-size barcodes, purchase orders, BOMs, batch tracking and manufacturing. It specifically supports apparel inventory and contract manufacturing. Cin7 Cin7

It can also track raw materials → work in progress → finished goods and production runs, which is much closer to what you'd eventually want from a fashion ERP. Cin7 Cin7

How I'd rank the options

The important distinction is that Shopify is primarily your selling system, whereas Katana/Cin7 are much better suited to answering questions like:

"I sold 17 black medium jackets. How many finished ones do I have left, how much fabric do I need for the next 50, which production run are they from, and what do I need to order from my manufacturer?"

For a fashion designer, I'd build your SKU system before loading products into the store. Your SKU should identify the actual sellable variant, while your production-run number should identify the manufacturing batch. That gives you much cleaner inventory and costing later.

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 online, I can recommend the exact setup and SKU/production-run structure I'd use.

For a small fashion label with custom tags, size/color variants, and limited production runs, I’d avoid choosing an ecommerce platform based on storefront features alone. Your key requirement is really inventory + SKU + production management.

My recommendation: Shopify + Katana

I’d start with Shopify for the storefront and Katana for production/inventory.

Shopify is excellent for selling the collection, while Katana can act as the operational layer: orders flow from Shopify into Katana, inventory stays synchronized, and production can be planned around those orders. Katana Katana

A typical setup could look like:

Shopify
→ customer orders
→ product variants/SKUs
→ payments & shipping
→ online storefront

Katana
→ fabric/trims/tag inventory
→ bills of materials
→ production runs
→ work-in-progress
→ finished garments
→ production/fulfillment inventory

That separation is particularly useful for fashion because a SKU such as JKT-BLK-S isn't just "one product" operationally. It may consume fabric, lining, zipper, thread, your custom neck tag, care label, packaging, etc.

Another strong option: Cin7 Core

If you're expecting the business to become more operationally complex fairly quickly, I'd look seriously at Cin7 Core.

Cin7 is unusually well suited to apparel: it supports size grids, size-specific barcodes, ecommerce variants, BOMs, production, purchasing, and contract manufacturing. Cin7 Cin7

It can also track raw materials → WIP → finished goods and handle production planning, which becomes valuable once you're doing multiple production runs with different quantities. Cin7 Cin7

How I'd choose

One important thing for your custom tags

I'd structure your inventory so the tag itself is an inventory component, rather than just putting "custom tag" in a production note.

For example:

Garment SKU: DRS-001-BLK-S

BOM:

• Dress shell fabric — 2.1 yd
• Lining — 1.4 yd
• Zipper — 1
• Thread — X amount
• Woven neck label — 1
• Care label — 1
• Hangtag — 1
• Packaging bag — 1

Then a production run of 100 dresses automatically tells you that you need roughly 100 neck labels, 100 care labels, 100 hangtags, etc. That's the kind of workflow where a manufacturing/inventory system starts paying for itself.

For your specific situation, I'd probably start with Shopify + Katana unless you already know you'll be doing substantial wholesale, multiple manufacturers, or complicated production. Cin7 is more powerful, but that power also means more operational overhead.

If you tell me roughly how many styles, SKUs, units per production run, and whether you're manufacturing yourself or using a cut-and-sew factory, I can recommend the exact setup—and tell you whether Katana, Cin7, or just Shopify is sufficient.

Katana
→ fabric/trims/tag inventory
→ bills of materials
→ production runs
→ work-in-progress
→ finished garments
→ production/fulfillment inventory

That separation is particularly useful for fashion because a SKU such as JKT-BLK-S isn't just "one product" operationally. It may consume fabric, lining, zipper, thread, your custom neck tag, care label, packaging, etc.

Another strong option: Cin7 Core

If you're expecting the business to become more operationally complex fairly quickly, I'd look seriously at Cin7 Core.

Cin7 is unusually well suited to apparel: it supports size grids, size-specific barcodes, ecommerce variants, BOMs, production, purchasing, and contract manufacturing. Cin7 Cin7

It can also track raw materials → WIP → finished goods and handle production planning, which becomes valuable once you're doing multiple production runs with different quantities. Cin7 Cin7

How I'd choose

One important thing for your custom tags

I'd structure your inventory so the tag itself is an inventory component, rather than just putting "custom tag" in a production note.

For example:

Garment SKU: DRS-001-BLK-S

BOM:

• Dress shell fabric — 2.1 yd
• Lining — 1.4 yd
• Zipper — 1
• Thread — X amount
• Woven neck label — 1
• Care label — 1
• Hangtag — 1
• Packaging bag — 1

Then a production run of 100 dresses automatically tells you that you need roughly 100 neck labels, 100 care labels, 100 hangtags, etc. That's the kind of workflow where a manufacturing/inventory system starts paying for itself.

For your specific situation, I'd probably start with Shopify + Katana unless you already know you'll be doing substantial wholesale, multiple manufacturers, or complicated production. Cin7 is more powerful, but that power also means more operational overhead.

If you tell me roughly how many styles, SKUs, units per production run, and whether you're manufacturing yourself or using a cut-and-sew factory, I can recommend the exact setup—and tell you whether Katana, Cin7, or just Shopify is sufficient.

For a small fashion label, I’d avoid jumping straight into a heavyweight ERP. Your key question is whether you need e-commerce + inventory, or e-commerce + actual production management.

My recommendation: Shopify + a production/inventory layer

shopify.com is the best starting point for most small clothing brands. It handles product variants and SKUs well—each size/color combination can have its own SKU—and supports inventory across locations. Shopify Help Center Shopify App Store

For example:

• TEE-001-BLK-S
• TEE-001-BLK-M
• TEE-001-BLK-L
• TEE-001-IVR-S

Then add a production-focused system once you're actually running manufacturing.

If production runs are central: Cin7 Core

cin7.com would be my strongest choice if you're doing things like:

• 100 units of Style A in a particular colorway
• tracking fabric, labels, buttons and packaging as components
• creating a bill of materials (BOM) for each garment
• sending production to a cut/sew factory
• tracking production jobs and finished inventory
• knowing how many units you can actually produce from your available materials

Cin7 specifically supports BOMs, component inventory, production jobs, purchase orders, size grids, barcodes and contract manufacturing. It can also connect with Shopify. Cin7 Cin7 Katana

So your setup could look like:

Shopify → customer orders → Cin7 → materials/production → finished garments → Shopify inventory

That's much more robust than trying to make Shopify itself manage your manufacturing.

Another option: Shopify + Katana

katanamrp.com is worth considering if you want something more focused on MRP/manufacturing rather than a broad inventory/ERP platform. Its Shopify integration is designed to send orders into Katana for production planning while keeping inventory synchronized. Katana

I'd think about the choices this way:

One important distinction: custom tags don't really require specialized e-commerce software. I'd structure the SKU around the garment/style + color + size, while treating things like woven labels, hangtags and packaging as production components. That keeps your inventory system from becoming a mess.

If you tell me roughly how many styles/SKUs you're launching, whether you manufacture yourself or use a cut-and-sew factory, and whether you'll sell wholesale, I can recommend the exact setup (including what I'd use for production runs, POs, BOMs, barcodes and custom labels).

For a small fashion line with custom tags, multiple sizes/colors, and production runs, I’d avoid choosing an ecommerce platform based on storefront features alone. Your bigger challenge will be SKU/variant control, raw materials, production batches, and knowing exactly how many finished units you can sell.

My recommendation: Shopify + Katana

Shopify is the best storefront starting point, while Katana can sit behind it as your production/inventory system.

• Shopify: website, checkout, customer orders, product variants and basic SKU management. Shopify specifically recommends unique SKUs for accurate inventory tracking and fulfillment. Shopify Help Center
• Katana: production planning, raw materials, purchase orders, inventory, manufacturing orders and production scheduling. Its Shopify integration is designed to send Shopify orders into Katana for production/fulfillment while keeping inventory synchronized. Katana Katana
• This is particularly useful if, for example, one "Luna Dress" comes in 4 sizes × 3 colors, but your production run involves fabric, labels, buttons, zippers, and packaging that need to be purchased separately.

Another strong option: Shopify + Cin7 Core

Cin7 is the one I'd investigate if you expect the operation to become more complex—especially wholesale, multiple sales channels, larger SKU counts, or more sophisticated inventory management.

Cin7 Core supports SKUs, BOMs, manufacturing, purchase orders and inventory, and its Shopify integration synchronizes products, orders and stock. Cin7 Help Center Cin7 Cin7 also specifically markets its system for fashion/apparel businesses and production/sourcing workflows. Cin7

How I'd choose

One important distinction: your SKU should identify the sellable finished variant, while your production system should separately track the materials/BOM and production batch. For example:

JKT-01-BLK-S → finished jacket SKU
FAB-BLK-001 → fabric
TAG-JKT-01 → custom woven tag
BATCH-2026-04 → production run

That separation will save you a lot of headaches when you reorder fabric, change suppliers, or produce the same style again.

If I were launching your line today, I'd start with Shopify + Katana, unless you already know you're going to have significant wholesale/multichannel complexity. Katana is purpose-built to make Shopify the storefront while it acts as the inventory/production hub. Katana

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 recommend the exact setup and SKU/production-run structure I'd use.

For a small fashion label with custom tags and limited production runs, I’d start with Shopify, and add a dedicated inventory/production system only when your manufacturing complexity justifies it.

My recommendation

1. Shopify — best starting point

Shopify is a strong fit if you’re primarily selling DTC online. You can give every size/color combination its own SKU, track inventory by variant, bulk-edit/import SKUs, and manage inventory across locations. Shopify Help Center Shopify Help Center Shopify Help Center

For example:

• JKT01-BLK-S
• JKT01-BLK-M
• JKT01-BLK-L
• JKT01-IVR-S

That works nicely with custom sewn-in labels, hangtags, barcodes, and packing/fulfillment because the SKU becomes the common identifier from production → inventory → sale.

The catch: Shopify itself isn't really a production-management/MRP system. If you need to track fabric → cut → sew → finished garments → production batch, you'll eventually want something alongside it.

2. Cin7 — best if production management is equally important

Cin7 is much more appropriate if by "production runs" you mean things like:

Order 150 units of Style 001 → consume 300 yards of fabric → assign production run → receive 145 finished units → track costs and inventory.

It supports bills of materials, production jobs, material consumption, batch/lot tracking, contract manufacturing, and apparel-specific size grids. Cin7 Cin7

You can also connect it to Shopify, so Shopify handles the customer-facing store while Cin7 handles the operational inventory/production layer. Cin7

The downside is cost and complexity. For a tiny first collection, it may be overkill.

What I'd do in your position

One particularly important distinction for a clothing line: don't make your SKU equal your production run. Keep the SKU tied to the sellable item (JKT01-BLK-M) and track the manufacturing batch separately (RUN-2026-01, for example). That way, if you produce the same jacket again six months later, you don't have to create a completely new SKU.

I'd also design your SKU + tag/barcode system before ordering your first batch of custom labels. Shopify explicitly recommends unique SKUs for each variant, and those SKUs can be used with third-party systems. Shopify Help Center

Bottom line: I'd launch on Shopify unless you already know your operation will involve significant cut/sew production, BOMs, multiple suppliers, and production tracking. In that case, Shopify + Cin7 is the more scalable setup. Cin7 Cin7

If you tell me roughly how many styles you're launching, how many units per style, whether you're manufacturing yourself or using a factory, and whether you're selling wholesale, I can recommend the exact setup—including how I'd structure your SKUs, production-run numbers, barcodes, and custom tags.

For a small fashion label with custom garment tags, I’d choose Shopify as the ecommerce foundation—but I’d pair it with a lightweight production/inventory app once your production runs become more complex.

shopify.com is particularly strong for your use case because each size/color combination can have its own SKU, inventory can be tracked by location, and Shopify supports purchase orders and supplier information. Shopify Help Center Shopify Help Center Shopify Help Center

My shortlist

Why Shopify gets my vote: You can structure something like:

STYLE-COLOR-SIZE
DRS01-BLK-S
DRS01-BLK-M
DRS01-RED-S

Each variant gets a unique SKU, while your custom sewn-in tag can carry the SKU/barcode or a separate internal product code. Shopify explicitly supports unique SKUs per variant and bulk SKU editing/import. Shopify Help Center

For production, I'd keep a distinction between finished-goods SKUs and production runs. For example:

• SKU: DRS01-BLK-M
• Production run: DRS01 / Black / Sept-2026 / 50 units
• Supplier: Factory A
• Cut quantity: 55
• Finished quantity: 51
• QC rejects: 4
• Available: 51

Shopify's native purchase orders are useful for ordering from suppliers and tracking incoming inventory, but if you need true cut/sew/finish workflows, bills of materials, work orders, material consumption, or production batches, I'd add a fashion-oriented inventory/production system rather than forcing Shopify to do all of that. Shopify itself highlights integrations with fashion-focused PLM and inventory tools for design-to-production workflows. Shopify

When I'd choose BigCommerce instead

bigcommerce.com is worth considering if you expect a large number of variants or wholesale/B2B sales. Its catalog model treats variants as inventory-tracked SKUs, and it supports substantial variation complexity. BigCommerce BigCommerce

For a new independent clothing line, though, I wouldn't choose it over Shopify unless you already know you'll need those more advanced catalog/B2B capabilities.

Bottom line: Start with Shopify + a production/inventory app, rather than buying an expensive full ERP. That gives you a clean customer-facing store while keeping your SKU, purchase-order, and production-run data structured enough to scale.

If you tell me roughly how many styles × colors × sizes you expect, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can recommend the specific Shopify production/inventory stack I'd use.

For a small fashion label, I’d avoid jumping straight into a heavy ERP. Your key requirements are slightly different from a typical ecommerce store: you need style/color/size SKUs, production runs, raw materials, finished-goods inventory, and custom tags/labels.

My recommendation

1. Best overall: Shopify + Cin7 Core

This is the setup I’d choose if you expect the line to grow.

shopify.com gives you the customer-facing store, while cin7.com handles the operational side.

Cin7 Core supports manufacturing, purchasing, suppliers, inventory, and multi-location stock, while syncing products, variants, SKUs and orders with Shopify. Shopify App Store Cin7

That means you could structure something like:

• Style: FD-101 Linen Trouser
• Color: Black
• Size: XS
• SKU: FD101-BLK-XS
• Production run: RUN-001
• Quantity produced: 50
• Materials: 120m fabric + 50 labels + 50 buttons
• Finished inventory: 50 → 47 → 42 as orders come in

That's much closer to how a clothing business actually operates than treating every product as a simple Shopify listing.

2. Best if you're very small: Shopify alone

If your first collection is something like 5–15 styles, a few sizes/colors, and relatively small production runs, I'd start with Shopify and keep production planning in a lightweight spreadsheet.

Shopify has proper SKU/variant inventory management, including separate SKUs for each size/color combination. Shopify Help Center

For example:

DRESS01-BLK-S
DRESS01-BLK-M
DRESS01-BLK-L
DRESS01-IVR-S

This is probably the least expensive and least overwhelming way to launch.

Then add dedicated inventory/production software when spreadsheets start becoming painful.

3. If production management is your main concern: Cin7

If you're actually manufacturing garments yourself or coordinating multiple factories, I'd lean toward Cin7 sooner. It specifically markets its system to fashion/apparel businesses and includes sourcing/production workflows alongside inventory management. Cin7

It's more infrastructure than you may need on day one, though. Cin7 Core currently starts around $349/month, according to its Shopify App Store listing. Shopify App Store

What I'd do in your position

One important point: custom tags don't need to drive your ecommerce choice. I'd make the SKU system the backbone and have your hangtags, woven labels, barcode labels, production sheets, and Shopify variants all reference the same SKU.

For example, FD101-BLK-M should mean the same thing everywhere—from your manufacturer's PO to the sewn-in label to the barcode scanned when you ship an order.

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 recommend the exact setup (including a SKU structure and production-run workflow) without overbuilding your tech stack.

For a small fashion line, I’d start with Shopify, then add a manufacturing/inventory system only when your production workflow becomes complex.

My recommendation

1. Shopify — best starting point for you

Shopify handles the customer-facing store and gives every size/color combination its own variant, inventory quantity, and SKU. You can also bulk-import/edit SKUs via CSV. Shopify Help Center Shopify Help Center

For example:

• JKT-01-BLK-S
• JKT-01-BLK-M
• JKT-01-BLK-L
• JKT-01-CREAM-S

That's particularly useful for custom garment tags because your SKU can become the internal identifier printed on the tag/barcode. Shopify explicitly recommends unique SKUs for each variant. Shopify Help Center

shopify.com

2. Cin7 — better once production becomes the hard part

If by "production runs" you mean things like:

"I'm producing 75 units of this style, using 2 yards of fabric per garment, with a particular trim/label, and 20 units are currently in production."

…then I'd look seriously at Cin7.

Cin7 is specifically geared toward apparel and supports size grids, variant syncing, BOMs, production jobs, raw-material tracking, batch/lot tracking, and contract manufacturing. Cin7 Cin7 Cin7

cin7.com

What I'd actually build

For a small designer brand, I'd use:

Shopify → selling/customer orders
Cin7 → inventory, materials & production
Accounting software → bookkeeping

But don't start with Cin7 just because it has more features. If you're doing relatively small runs and your manufacturer gives you production reports, Shopify alone may be considerably easier.

The key question is how you manufacture. If you tell me:

• roughly how many styles/SKUs you expect,
• typical production run size (e.g. 25, 100, 500 units),
• whether you manufacture yourself or use a cut-and-sew factory,
• whether you need to track fabric/trims/labels as raw materials,
• and whether you want barcode scanning,

I can tell you whether Shopify alone, Shopify + an inventory app, or Shopify + Cin7 makes the most sense for your line.

2. Cin7 — better once production becomes the hard part

If by "production runs" you mean things like:

"I'm producing 75 units of this style, using 2 yards of fabric per garment, with a particular trim/label, and 20 units are currently in production."

…then I'd look seriously at Cin7.

Cin7 is specifically geared toward apparel and supports size grids, variant syncing, BOMs, production jobs, raw-material tracking, batch/lot tracking, and contract manufacturing. cin7.com cin7.com cin7.com

cin7.com

What I'd actually build

For a small designer brand, I'd use:

Shopify → selling/customer orders
Cin7 → inventory, materials & production
Accounting software → bookkeeping

For a small fashion label with custom woven labels/tags, multiple color-size variants, and planned production runs, I would avoid choosing ecommerce software based only on the storefront. You need something that can handle:

• Style → color → size SKU matrices
• Purchase orders to manufacturers
• Production runs / work orders
• Materials (fabric, trims, labels, packaging)
• Costing and margins
• Pre-orders and launch drops
• Inventory by channel (website, pop-ups, wholesale)

Apparel is tricky because one “style” can explode into dozens of SKUs, and generic inventory tools often become spreadsheet-heavy once you scale. AIMS360 Fulfil

Best fits for a small clothing line

1. shopify.com + a production/inventory app

Best starting point for most emerging designers

Good if you:

• Sell primarily direct-to-consumer
• Launch small collections or drops
• Use outside factories/sewers
• Need a beautiful storefront quickly

Strengths:

• Excellent ecommerce experience
• Strong ecosystem for apparel apps
• Easy SKU/variant management
• Good for pre-orders and limited releases

Weakness:

• Shopify itself is not a full apparel production system; once you are managing raw materials, manufacturing milestones, and complex wholesale, you may need an ERP layer. Uphance

Pair it with:

• katanamrp.com — better for production planning, bills of materials, and tracking materials-to-finished-goods workflows. EGNITION
• prediko.io — useful for inventory forecasting and replenishment if you are Shopify-first. Prediko

My pick if you are launching your first collection: Shopify + Katana.

2. apparelmagic.com

Best if you want fashion-specific operations from day one

Designed around apparel workflows:

• Style/color/size grids
• Production orders
• Materials
• Costing
• Inventory
• Wholesale

It is more “fashion business management” than just ecommerce. It is often a better fit than generic inventory software once you have multiple collections. AIMS360

3. uphance.com

Best for a growing designer brand moving toward wholesale

Useful if you expect:

• Boutique accounts
• Seasonal collections
• More structured production calendars
• Larger SKU counts

It combines apparel workflows with inventory and production tools. The Retail Exec

4. aims360.com or syncfashion.com

Best later-stage options

These are more appropriate when you have:

• Hundreds/thousands of SKUs
• Multiple factories
• Wholesale retailers
• EDI requirements
• Dedicated operations staff

They may be overkill for a first launch. Software Advice AIMS360

What I would choose based on your stage

Set up your SKU system early

For fashion, I would create SKUs like:

JKT-001-BLK-M

Meaning:

• JKT = product category
• 001 = style number
• BLK = color
• M = size

Also track:

• Fabric supplier
• Label/tag version
• Factory
• Production batch number
• Cost per unit
• Planned delivery date

For a new designer brand, I would probably start with Shopify as the customer-facing store and Katana or ApparelMagic as the operations backbone, depending on whether you are more focused on manufacturing or fashion-specific workflows. Thewearify

If you tell me your expected launch size (e.g., 3 styles vs 30 styles, made-to-order vs inventory, and whether you’ll use a factory or sew yourself), I can narrow this to one setup.

• JKT = product category
• 001 = style number
• BLK = color
• M = size

Also track:

• Fabric supplier
• Label/tag version
• Factory
• Production batch number
• Cost per unit
• Planned delivery date

For a new designer brand, I would probably start with Shopify as the customer-facing store and Katana or ApparelMagic as the operations backbone, depending on whether you are more focused on manufacturing or fashion-specific workflows.

For a small fashion line, I’d choose Shopify + Katana rather than trying to make one system do everything.

My pick: Shopify + Katana

Shopify is the customer-facing ecommerce system, while Katana becomes your production/inventory system.

• Shopify: storefront, checkout, customers, orders, product variants, and SKU-level inventory. Shopify supports variants such as size × color and inventory tracking at the variant level. Shopify Help Center
• Katana: materials, bills of materials (BOMs), manufacturing orders, purchasing, production scheduling, and inventory.
• Custom tags: I'd treat your garment tag/label as a component in the BOM rather than creating a separate sellable SKU for every tag.
• Production runs: Katana supports both make-to-stock and make-to-order manufacturing orders, which is useful for doing, say, a 50-piece run of a jacket while still handling individual customer orders. Katana Katana
• SKU synchronization: Shopify products can be imported into Katana and matched by SKU; inventory can then sync back to Shopify. Katana Katana

How I'd structure your line

For example, suppose you launch:

"Studio Jacket"

• STJ-BLK-XS
• STJ-BLK-S
• STJ-BLK-M
• STJ-BLK-L
• STJ-IVY-XS
• etc.

In Katana, the BOM for each variant could include:

• Outer fabric — 1.4 yd
• Lining — 1.2 yd
• Zipper — 1
• Woven neck label — 1
• Main hangtag — 1
• Care label — 1
• Packaging — 1

Then a 50-unit production run tells you what materials you need and lets you track the finished units separately from your raw materials.

That's particularly valuable for a fashion business because you're really managing three different inventories: finished garments, production materials, and branded components such as labels/tags.

When I would not use Katana

If you're initially very small—for example, 10–20 SKUs, one production partner, and a couple of small drops per year—I'd start with Shopify alone and keep production planning in a spreadsheet. Adding an MRP system too early can create unnecessary complexity.

I'd move to Shopify + Katana when you're dealing with things like:

• Multiple colors/sizes and dozens of SKUs
• Repeat production runs
• Fabric and trim purchasing
• Contract manufacturers
• Wholesale + DTC simultaneously
• Needing to know "How many more units can I make from the materials I have?"
• Wanting production quantities and actual inventory to update your online store automatically

Katana specifically supports Shopify orders flowing into production and can keep inventory aligned between the two systems. Katana Katana

Bottom line: For a serious small clothing label, Shopify for selling + Katana for production/inventory is the setup I'd pick. It gives you a clean path from customer order → SKU → materials → production run → finished inventory → fulfillment without jumping immediately into an enterprise fashion ERP. Katana

If you tell me roughly how many SKUs you're launching, whether you manufacture yourself or use a factory, and whether you're doing DTC, wholesale, or both, I can narrow this down to the best 2–3 systems for your specific workflow.

For a small fashion label with custom tags and limited production runs, I’d choose Shopify + a lightweight manufacturing/inventory system, rather than trying to make Shopify do production planning by itself.

My top choice: Shopify + Katana

shopify.com is the best storefront foundation for your situation. It handles size/color variants, unique SKUs, inventory, orders, and multiple locations well. Shopify specifically recommends a unique SKU for each variant—for example, each combination of style + color + size. Shopify Help Center Shopify Help Center

Then add katanamrp.com as your production/inventory hub.

Katana is particularly interesting for you because it can sit behind Shopify: Shopify handles the customer-facing store, while Katana manages inventory and production. Its Shopify integration syncs orders and inventory, and Katana supports manufacturing workflows, locations, purchasing, production planning, and barcodes. Katana Katana

That gives you a workflow roughly like:

Design → SKU → production run → raw materials → finished garments → Shopify inventory → customer order

For example:

TEE-01-BLK-S
TEE-01-BLK-M
TEE-01-BLK-L

You could have a production run of 50 units, with Katana tracking the materials and production while Shopify knows that 50 finished units are available for sale.

When I'd choose Cin7 instead

cin7.com becomes more attractive if you're expecting the operation to get substantially more complicated—multiple manufacturers, warehouses, wholesale accounts, lots of SKUs, or more sophisticated purchasing/production planning.

Cin7 explicitly targets fashion/apparel and supports raw-material sourcing, production, warehouse management, multichannel inventory, and 700+ integrations. Its manufacturing functionality includes BOMs, component tracking, production runs, batch/lot traceability, and MRP. Cin7 Cin7

For a small launch, though, I think Cin7 could be more system than you need.

What I'd pick for you

One important distinction: custom tags don't necessarily require special ecommerce software. If by tags you mean custom woven neck labels/hangtags containing your brand, style number, size, care information, etc., I'd make the SKU/style number the common identifier across your tag, production sheet, inventory system, and Shopify. That will save you a huge amount of confusion later.

If you tell me roughly how many styles × colors × sizes you're launching, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can recommend the exact setup—including how I'd structure your SKUs and production-run numbers.

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

My pick: Shopify + Cin7 Core

shopify.com is the storefront, while cin7.com becomes your operational system of record.

That combination is particularly strong for your use case because Cin7 can handle:

• SKUs and variants — e.g. JKT-BLK-S, JKT-BLK-M, JKT-CRM-M.
• Size grids and per-size barcodes, which are important for apparel. Cin7
• Bills of materials (BOMs) — fabric, lining, buttons, custom woven label, hangtag, packaging, etc.
• Production jobs/runs — so a run of 100 jackets can consume the appropriate quantities of materials and create finished inventory.
• Contract manufacturing, including outsourced production. Cin7
• Purchase orders and raw-material purchasing.
• Syncing inventory and orders with Shopify in real time. Cin7

Cin7 specifically positions its apparel solution around sourcing, production, inventory and ecommerce, rather than simply being a retail inventory database. Cin7

How I'd structure your products

For example, suppose you make a Linen Overshirt:

Finished-product SKUs

• LSH-BLK-S
• LSH-BLK-M
• LSH-BLK-L
• LSH-IVY-S
• LSH-IVY-M
• LSH-IVY-L

Then the production BOM could contain:

• 1.4 yd linen
• 0.3 yd lining
• 8 buttons
• 1 woven neck label
• 1 care label
• 1 hangtag
• 1 polybag

A production run of 50 units would tell the system what materials need to be available and what finished SKUs should result. Cin7 supports BOMs, production scheduling and material planning for exactly this kind of workflow. Cin7 Cin7

Other options I'd consider

Cin7 itself describes Core as its more turnkey solution for SMBs and Omni as the more customizable option for complex, scaling businesses. Cin7

One caveat: Cin7 is substantially more sophisticated than a basic Shopify inventory setup, so I wouldn't buy it just because you have SKUs. If you're launching with, say, 5 styles × 4 sizes × 3 colors and producing small batches yourself, you may be able to start simpler and migrate once production becomes painful.

The deciding question is how you manufacture. If you tell me roughly how many styles/SKUs you're launching, whether you're manufacturing yourself or using a factory, and your expected first production quantity, I can recommend the simplest setup that won't become a nightmare when you do your second collection.

For a small fashion label, I’d strongly consider Shopify + Katana rather than trying to make one ecommerce platform do everything.

My pick: Shopify + Katana

shopify.com is the storefront/customer-facing system, while katanamrp.com handles the more manufacturing-oriented inventory and production side.

That combination is particularly well suited to what you described:

• SKUs: Shopify gives every size/color variant its own SKU, and supports bulk SKU editing/import. Shopify Help Center
• Custom garment tags: I'd make the SKU/barcode on your physical hangtag match the SKU in Shopify/Katana. This makes receiving, counting, picking and returns much easier.
• Production runs: Katana is designed around materials, production planning, manufacturing and inventory—not just selling finished products. Katana Support Katana Support
• Small-batch manufacturing: You can model a garment's components/materials and track what you've produced versus what remains available.
• Factory/contract manufacturer: Katana specifically supports outsourced manufacturing workflows, including transferring materials to a contractor and tracking inventory there. Katana Support
• Automatic ecommerce sync: Shopify orders can flow into Katana, while inventory can sync back to Shopify so your online stock reflects what's actually available. Katana Support Katana Support
• Purchase orders: Shopify itself now has supplier/PO functionality, so you can handle purchasing without immediately adding another system. Shopify Help Center

How I'd structure your fashion SKUs

For example, suppose you launch a jacket:

Product: Studio Cropped Jacket
Color: Black
Size: Medium

I'd give the sellable unit something like:

SCJ-BLK-M

Then:

• SCJ-BLK-XS
• SCJ-BLK-S
• SCJ-BLK-M
• SCJ-BLK-L
• SCJ-BLK-XL

Your physical garment tag can carry the SKU plus a barcode/UPC.

The important distinction is that I'd not put the production-run number into the SKU. If you make 50 black medium jackets in Run 01 and another 75 six months later, they should generally remain SCJ-BLK-M; the production/batch information belongs in your manufacturing/inventory records.

When I'd choose something else

The key question is how sophisticated your production needs are. If you're making, say, 5–20 styles with several colors/sizes and doing occasional 50–300 unit production runs, I wouldn't start with a giant ERP. Shopify + Katana gives you a fairly clean progression from design → BOM/materials → production run → finished SKU → online sale → inventory deduction.

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 need wholesale, I can narrow this down to the best 2–3 setups and explain the likely cost/complexity of each.

For a small fashion label, I’d separate ecommerce from production/inventory management rather than expect one platform to do everything.

My pick: Shopify + Cin7 Core

Shopify is the strongest choice for the storefront, checkout, customer orders, and product variants. Shopify has also been improving its native purchasing and inventory workflows in 2026. Shopify

Then use Cin7 Core as the operational layer. It is particularly well suited to apparel because it supports size grids, per-size barcodes, ecommerce variants, BOMs, production jobs, contract manufacturing, and raw-material tracking. Cin7 Cin7

That gives you a workflow roughly like:

Design → SKU → BOM → production run → finished inventory → Shopify → customer order

For example, instead of treating “Black Oversized Tee” as one SKU, you could have:

• TEE-BLK-S
• TEE-BLK-M
• TEE-BLK-L
• TEE-BLK-XL

And your production record can specify something like 100 units, with the fabric, labels, hangtags, trims, labor, and other components attached to the production run. Cin7 supports BOM tracking and can track raw materials through production into finished goods. Cin7 Cin7

When I'd choose something simpler

If you're very early—say, 10–30 styles, one manufacturer, and relatively small production runs—I would actually start with Shopify alone and avoid paying for an ERP prematurely. You can establish a clean SKU convention and add manufacturing software once spreadsheets start becoming painful.

If you're already coordinating multiple fabrics/colors/sizes, purchase orders, manufacturers, production batches, and reorder decisions, I'd go directly to Shopify + Cin7 Core.

Cin7 specifically supports contract manufacturing and capacity planning, which becomes useful when you're sending production to outside factories. Cin7

One important consideration for custom tags

I'd model the garment and its packaging/branding components separately rather than burying everything in the SKU.

For example:

Finished SKU: JKT-OLV-S

BOM:

• Olive jacket shell
• Lining
• Zipper
• Woven neck label
• Size label
• Hangtag
• Care label
• Packaging

That lets you answer questions like “We have enough jackets to fulfill 200 orders, but only 130 custom hangtags—what's actually holding up production?” That's where manufacturing-oriented software becomes much more valuable than a basic ecommerce platform.

Bottom line:

• Just launching: Shopify
• Launching with serious production tracking: Shopify + Cin7 Core
• Complex manufacturing / many suppliers / multiple warehouses: Cin7 becomes increasingly compelling; its current Core offering includes BOMs, manufacturing, SKU management, purchasing, and ecommerce integrations. Cin7

shopify.com · cin7.com

If you tell me roughly how many styles/SKUs you're launching, your production run size, and whether you're manufacturing yourself or using a factory, I can narrow this down to the best setup (including lower-cost alternatives).

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.