Crystal velour
A1# red · 1 mm pile
Dongguan · 1-001
156 m
Fabric Trading ERP Case Study: How to Run Purchasing, Warehousing, and Stock Moves on One Ledger?
CASE STUDY · FABRIC TRADE ERP
A warehouse-first ERP for fabric traders: color, pile, bin location, inbound receipts, outbound issues, and stocktake share one inventory fact line—so floor staff can reconcile on site, and management sees live stock instead of a lagging spreadsheet.
WAREHOUSE · LIVE STOCK
Openinginbound
Purchaseinbound
Transferinbound
Salesoutbound
Velvet
A2# blue · 2 mm pile
Dongguan · 1-014
88 m
Silk pile
B3# green · 1 mm pile
Dongguan · 2-006
210 m
Purchase inbound waiting
Why this work
When orders fragment, paper stock cannot keep up with the floor
Fabric is not one SKU name. The same article splits by color, pile, dye lot, and bin. Purchasing, sales, transfers, and stocktake each keep their own notes. Once volume rises, relying on a few people who “just know the warehouse” stops working.
货号色卡毛高仓位
Identity
A roll must carry article, color, pile, and bin at once
Buyers order on mill codes, warehouse staff receive in pieces and meters, sales quote by color card. When the three names drift, the stock number looks complete but no longer maps to a shippable roll.
What you can sell is not “in stock”—it is meters available in a color at a bin.
Latency
The ledger updates after the floor has already moved goods
Inbound, outbound, and transfers live in separate sheets or chat threads. Book stock lags by hours or days. Warnings are verbal; oversell shows up only at month-end.
Turnover depends on who remembers the last move, not on a live balance.
采购
销售
仓配
Handoffs
Purchasing, sales, and warehouse each run a private line
Purchase orders, mill shipments, inbound lines, sales issues, and shortage issues sit with different people. Matching source documents is manual; exceptions are chased in group chat.
Coordination becomes a reconciliation meeting instead of documents lining up in the system.
?
Risk
When stocktake misses, the gap has no business story
Period-end counts only show book versus physical. If purchase inbound, sales outbound, and transfers are not expanded on the same basis, the gap is guessed—and cost risk rolls into the next period.
A count must unfold current inbound and outbound before a variance can be explained.
Fabric trading needs one fact base for spec masters, bin stock, and warehouse documents so floor work can keep up with fragmented orders.
How we redesigned it
We redesigned the fact line from inbound to outbound
This is not another inventory spreadsheet. Each roll gets a stable spec identity, then inbound, outbound, transfer, and stocktake post continuously to that identity.
How it used to run
Mill codes, internal names, and color cards kept separately
Receipts in one sheet, sales deductions in another
Bin locations in sticky notes or someone’s memory
Tasks chased by phone and chat
Month-end: force several sheets together
The rebuilt loop
Article, color, pile, and bin as one SKU identity
Inbound posted by type, tied to source and mill shipment
Sales, shortage, and transfer outbound share one stock deduction
Open documents land in the warehouse inbox
Stocktake unfolds current moves so a gap can be traced
Floor staff complete receive, issue, and count. Management sees balances, alerts, and tasks from the same stock ledger.
What we shipped
One warehouse ERP covering pick, inbound, outbound, and count
Capabilities follow floor work: identify the roll, then make inbound, outbound, and stocktake traceable—not a menu of modules.
A1#1-001
采购入库厂家发货落架 1400 米
- 销售出库
- 亏空出库
- 调拨出库
+100+23-123
If this is you
If you are living these questions, this loop may fit
These are the stalls we see most often on a fabric warehouse floor.
1-001
When sales asks “do we still have this color?”, does someone have to walk the aisle?
Put color, pile, bin, and meters on one pick card so the answer does not wait on a physical search.
Goods arrived, but inbound type, mill shipment, and putaway still do not line up?
One inbound document holds source, purchase lines, mill shipment, and putaway, with meters or pieces as the unit.
Δ
The count is short tens of meters, and no one can say if sales over-issued or a transfer never posted?
Unfold current inbound and outbound on the count line; send the gap back to documents before adjusting the book.
Inbound and outbound waiting lists live in group chat and get missed?
Open sales issues, purchase receipts, and transfers go to a notification center, routed by document and warehouse.
How it works on the floor
From identifying a roll to counting it, one stock ledger on site
The sequence follows warehouse work. Screens are from the warehouse mini program: pick, inbound, outbound, stocktake, and inbox.
The floor completes receive, issue, and count. The system keeps one reconcilable stock fact line.
How it is built
Floor app, stock ledger, and masters on one chain
The mini program runs on-site work. The service holds SKU, bin, document state, and balances—without a second inventory table.
The warehouse client handles pick, receive, issue, and count. The stock engine posts by inbound and outbound type. Masters unify article, color, pile, warehouse, and rack.
Warehouse client
- Product search and bin confirm
- Inbound / outbound desks and document detail
- Stocktake unfold and inbox
Stock and documents
- Posting by inbound and outbound type
- Source, mill shipment, and putaway alignment
- Balance, alerts, and count gaps
SKUBINROLE
Masters and access
- Fabric spec and color masters
- Warehouse, rack, and role access
- Tasks routed by warehouse
Keywords
fabric ERPWMSlot inventorypurchase inboundsales outboundstocktakeUniAppNestJS
What was delivered
From several ledgers to a stock book the floor can run
We describe a checkable operating loop. We do not invent unauthorized turnover or accuracy percentages.
Fabric identity can be searched and confirmed on site
Article, color, pile, warehouse, rack, and meters sit on one pick card. Moves no longer depend on verbal matching.
INOUT
Inbound and outbound post by business type
Opening, purchase, transfer, other inbound, and sales, shortage, and transfer outbound are totaled separately, with source documents and owners.
Counts unfold current moves; tasks run on the phone
A variance is first compared with current inbound and outbound. Open documents land in the inbox, routed by warehouse.
Where else it fits
Other fabric operations that need the same stock fact line
Any trade or warehouse that manages color, lot, meters or pieces, and must receive, issue, and count on site can reuse this ledger.
Fabric and textile trading
Many colors, pile heights, and warehouses—purchase inbound and sales outbound must share one book.
Apparel trims and piece goods
Orders split by color and dye lot; available meters at a bin must be answerable on the floor.
Dyeing and finishing warehouses
Mill shipments, dye-lot variance, and putaway must align; counts must explain the period’s moves.
Regional transfer hubs
Transfer inbound and outbound are frequent; tasks need to reach the warehouse that owns the stock.
Next step
Your fabric stock can run on a ledger you can reconcile
If color identity, inbound matching, or stocktake gaps are the stall, start with one warehouse loop: identity, inbound, outbound, count.
- Name the loopPick → inbound → outbound → count
- Align the unitsMeters / pieces, color, and bin ownership
- Then extendTransfers, shortage, inbox, and roles
