PO Intake
Upload the received PO file as is. AI reads items and quantities per style, registers the order, and asks back only for values missing from the file.
Trim Orders Grouped
by Season Item
Mono:parts is a trims sourcing solution. It manages a brand's season trims as an item-level library, groups requests from many styles by item, and connects ordering, shipment and settlement.Mono:parts is a trims sourcing solution. It manages a brand's season trims as an item-level library and connects ordering, shipment and settlement.
AI Automation, Order to Settlement
AI registers PO files, fills in purchase prices, assigns material factories, enters shipping documents and calculates the monthly closing.
Staff check the filled values, then save.
AI reads PO files, which differ in format by brand, and registers style, item and quantity. It asks staff only for values missing from the file.
AI assigns a supplier to each line and fills in the purchase price and amount from the Library. Lines with a different supplier or currency get a separate PO.
Based on assignment history from earlier orders, AI assigns a material factory to each item and creates a PO sheet per factory.
Upload the packing list and waybill, and AI fills in shipped quantity, shipment date and waybill number. Unshipped quantity stays as balance.
AI separates overseas and domestic deliveries and bills only that month's shipments. Enter the month-end rate and KRW amounts are calculated.
Orders Read as One Item Line
Trim requests once issued per style are gathered by item. They share the same partner records with Monolis on the style axis.
For materials & trims ordering on the style axis, see Monolis. Monolis Materials & Trims Ordering
Upload the received PO file as is. AI reads items and quantities per style, registers the order, and asks back only for values missing from the file.
POs are split by style and supplier and sent with e-signature. The vendor branch assigns a material factory to each item and receives a PO sheet per factory.
Upload the packing list and waybill, and AI fills in shipped quantity, shipment date and waybill number. A partial shipment stays as balance.
A settlement statement is built from the month's shipments, split by overseas and domestic, with KRW at month-end rate.
Trim Vendor · Brand · Vendor Branch
Each role sees the same library at a different price.
Select a role tab to see the price layer and permissions of that role.
The trim vendor manages the library and Offer prices, checks brand orders, assigns vendor branches and handles the monthly closing.
The brand sees items at the Offer price, enters orders and requests them from the trim vendor.
A vendor branch sees and enters only its purchase price, picks the material factory, orders, and logs sewing factory shipments.
| VENDOR | BRAND | BRANCH | |
|---|---|---|---|
| LIBRARY | MANAGE | VIEW | VIEW |
| OFFER ₩ | VIEW | VIEW | |
| PURCHASE ¥ | VIEW | ENTER | |
| ORDER | CONFIRM | ENTRY | FACTORY |
| CLOSING | MONTHLY | REVIEW |
01 · DraftThe brand enters the order. Brands connected through their ERP send it automatically by mapping; other brands use Excel upload or direct entry. For brands without organized POs, the trim vendor enters the order for them.
02 · NewLines missing required values are flagged. Once filled and requested, the order reaches the trim vendor as New.
03 · In-prodThe trim vendor checks the order and assigns a vendor branch (edited from the per-item default). The vendor branch picks a material factory per item, enters the purchase price, then downloads each factory PO and sends it.
04 · In-ShippingThe vendor branch and the trim vendor register shipments by Tracking number and record partial shipments (Partial) per item.
05 · ShippedWhen all items are shipped, the status changes to Shipped and is reflected in settlement and the Master Chart.
06 · ClosedAt month end the vendor branch reconciles purchases, and the trim vendor closes the month by shipment month and issues invoices.
CancelOnly the trim vendor can set Urgent or Cancel and delete a PO. A brand can also delete an order in Draft status.
SaaS with No Separate Build
With no build project, brands and vendor branches start ordering in the same library as soon as the trim vendor issues accounts. Calculation and integration are the same standard features.
| Account Type | Trim Vendor · Brand · Vendor Branch |
| Price Access | Offer price for brands, Purchase price for branches |
| Account | 1 account per user, session limit |
| Account Admin | Trim vendor sets expiry date and active status per account |
| Language | English by default; item names in Korean, English, Chinese |
| Hosting | Cloud SaaS, used once accounts are issued |
| Devices | Web |
| Input · Brand | Excel PO upload, read and registered by AI |
| External ERP | Brand ERP orders received and auto-mapped |
| Menu Links | Library · Order · Production · Shipment · Settlement |
| Stock Link | Order qty deducted, shortage alert |
| Packing Link | Cartons auto-linked to shipments |
| Shipping | Split shipment, Tracking number recorded |
| Monolis | Covers trims within materials & trims ordering |
Enter the FOB unit price in the library and the amount with tax is calculated.
Sums per-style request quantities and calculates item order quantity with consumption (YY) and Loss.
Stock is deducted as orders are placed, with an alert on shortage. Items packed in cartons carry over to shipment.
Orders to trim vendors follow the same standard, through shipment and settlement.
We propose the scope of Mono:parts
accounts to fit your brand and vendor branch setup.