Product Library

The Product Library is the reusable catalog behind every order. A style carries its tech packs and photos; materials define what it’s made of; the BOM (bill of materials) and BOL (bill of labor) list quantities and operations; and SKUs enumerate the color/size variants. Together they feed costing — nothing is priced without a BOM.

The flow

Styles

A style is the master record for a garment design. It anchors the tech packs, BOM, and SKUs.

GET /api/v1/styles
POST /api/v1/styles
GET /api/v1/styles/{sid}
PATCH /api/v1/styles/{sid}
Authorization: Bearer <access_token>

Create a style

name

string

required

Style name.

ref

string

Style reference code. Auto-generated if omitted.

POST /api/v1/styles
Authorization: Bearer <access_token>

{
  "name": "Heavyweight Crew Tee",
  "ref": "ST-CREW-001",
  "category": "tops"
}

Response (201):

{
  "id": "uuid",
  "ref": "ST-CREW-001",
  "name": "Heavyweight Crew Tee"
}

Look up by reference with GET /api/v1/styles/by-ref/{ref}.

Styles Files — tech packs & photos

Each style carries its construction documents and reference imagery.

GET  /api/v1/styles/{style_id}/tech-packs
POST /api/v1/styles/{style_id}/tech-packs
POST /api/v1/styles/{style_id}/tech-packs/links
GET  /api/v1/styles/{style_id}/photos
POST /api/v1/styles/{style_id}/photos
PATCH /api/v1/styles/{style_id}/photos/{photo_id}/set-primary
Authorization: Bearer <access_token>

Materials

Materials are the fabrics, trims, and accessories the BOM consumes. They are versioned and run through a draft → verify → submit workflow.

GET /api/v1/materials
POST /api/v1/materials
GET /api/v1/materials/{material_id}/detail
PATCH /api/v1/materials/{material_id}
Authorization: Bearer <access_token>

Get the next reference code with GET /api/v1/materials/next-ref. Material versions and verification run through POST /materials/{document_id}/verify and POST /materials/{document_id}/version.

BOM — Bill of Materials

The BOM lists every material a style consumes, with quantities and wastage. BOMs are versioned and gated by an approval workflow before they can drive costing or material requests.

GET /api/v1/bom
POST /api/v1/bom
GET /api/v1/bom/{bom_id}
PATCH /api/v1/bom/{bom_id}
Authorization: Bearer <access_token>

Add and assign line items

Line items live on a BOM version. Each line item is then linked to a concrete material.

POST /api/v1/bom/versions/{version_id}/line-items
PATCH /api/v1/bom/line-items/{line_item_id}
POST /api/v1/bom/line-items/{line_item_id}/assign-material

material_id

string

required

The material to assign to this BOM line item.

POST /api/v1/bom/line-items/{line_item_id}/assign-material
Authorization: Bearer <access_token>

{
  "material_id": "uuid"
}

Versioning & approval

POST /api/v1/bom/{bom_id}/submit
POST /api/v1/bom/{bom_id}/approve
POST /api/v1/bom/{bom_id}/reject
POST /api/v1/bom/{bom_id}/withdraw
POST /api/v1/bom/{bom_id}/versions
GET  /api/v1/bom/{bom_id}/versions/{version_a}/compare/{version_b}
GET  /api/v1/bom/{bom_id}/usage

GET /api/v1/bom/{bom_id}/usage shows which orders and cost sheets reference a BOM — check it before withdrawing or revising an approved BOM.

BOL — Bill of Labor

The BOL is the labor counterpart to the BOM: it lists the sewing operations and their times. Like the BOM, it is versioned and approved, and it can estimate labor cost directly.

GET  /bol
POST /bol
POST /bol/{bol_id}/estimate-labor
POST /bol/{bol_id}/submit-review
POST /bol/{bol_id}/approve
POST /bol/{bol_id}/reject
POST /bol/{bol_id}/create-version
GET  /bol/{bol_id}/compare
Authorization: Bearer <access_token>

POST /bol/{bol_id}/estimate-labor produces the labor figure that flows into the cost sheet — see Labor Cost in the Order Lifecycle page.

SKUs

SKUs enumerate the color/size variants of a style (and of materials). They are typically bulk-generated from the style’s option matrix rather than entered by hand.

GET  /api/v1/styles/{style_id}/skus
POST /api/v1/styles/{style_id}/skus
POST /api/v1/styles/{style_id}/skus/generate
GET  /api/v1/materials/{material_id}/skus
POST /api/v1/materials/{material_id}/skus/generate
Authorization: Bearer <access_token>

Bulk-generate style SKUs

POST /api/v1/styles/{style_id}/skus/generate
Authorization: Bearer <access_token>

{
  "colors": ["Black", "White"],
  "sizes": ["S", "M", "L", "XL"]
}

Response (201):

{
  "created": 8,
  "skus": [
    { "id": "uuid", "code": "ST-CREW-001-BLK-S" }
  ]
}

SKU Management

A separate SKU management surface handles label generation:

GET  /skus
POST /skus
POST /skus/pdf
POST /skus/qr_code
PUT  /skus/{row_id}
Authorization: Bearer <access_token>

See the API Reference tab for the full endpoint list.

Feeds into

Order Lifecycle

Approved BOM/BOL drive costing.

Procurement

BOM demand drives material requests.

​Product Library

​The flow

​Styles

​Create a style

​Styles Files — tech packs & photos

​Materials

​BOM — Bill of Materials

​Add and assign line items

​Versioning & approval

​BOL — Bill of Labor

​SKUs

​Bulk-generate style SKUs

​SKU Management

​Feeds into

Order Lifecycle

Procurement

Product Library

The flow

Styles

Create a style

Styles Files — tech packs & photos

Materials

BOM — Bill of Materials

Add and assign line items

Versioning & approval

BOL — Bill of Labor

SKUs

Bulk-generate style SKUs

SKU Management

Feeds into