How to Implement SAP Business One for Garment & Apparel Business (2026 Guide)

1Who SAP Business One fits

SAP Business One is a sound choice for small and mid-size garment makers and distributors that want one ledger, one stock value and a mature purchasing and inventory core, and that have a partner to fill the apparel gaps. It is SAP's ERP for smaller companies, sold and implemented through partners, and it runs on Microsoft SQL Server or SAP HANA.

Its strengths for a factory are the ones an accountant values: batches and serial numbers on stock, units of measure groups, landed costs, production orders with bills of materials, approval procedures and down payments. Its weakness for apparel is equally clear. SAP Business One has no standard colour and size matrix, so every size of every colour is its own item code unless an add-on provides a matrix. That one fact shapes most of the design decisions in this chapter.

Signs SAP Business One is a good choice

SAP Business One tends to work when the factory values a stable financial and inventory core over deep apparel features inside the ERP.

• The group already uses SAP, or the owner wants an SAP ledger that auditors and banks recognise.
• A partner with manufacturing and apparel experience is available, including someone who has installed a variant add-on before.
• The number of active styles, colours and sizes is known, and the item count it produces has been worked out (section 12).
• The country has an SAP Business One localisation that covers local tax and e-invoicing (section 23).

Signs to slow down

Slow down when the expectations placed on SAP Business One belong to a planning, floor or development system.

• Merchandisers expect to key orders into a colour-by-size grid, and nobody has chosen or priced an add-on.
• The factory expects production orders to balance sewing lines and track bundles.
• Several processes go out to subcontractors in a chain, and the project assumes a standard subcontracting order will handle it (section 18).
• The go-live date falls inside peak season.

2Why no ERP fits apparel on its own

No general ERP fits apparel out of the box, because an ERP is built around a known item with one bill of materials, while a garment order starts as a style that is quoted, sampled and approved before any item exists. SAP Business One meets this wall sooner than some ERPs because it has no item matrix: the style itself has no home in standard SAP Business One, only its finished item codes do. SAP S/4HANA, NetSuite, Dynamics 365 and Odoo meet the same wall in their own ways, which is why fashion add-ons and fashion-specific systems exist. The same wall stands in front of brands, buying agents and own-label retailers that never cut a garment, because their orders also start as styles, samples and approvals at factories they do not control (section 35).

An ERP is built around the transaction: a known item, a fixed bill of materials, a price, a receipt, an invoice. It is right to be strict about that, because strictness keeps the books correct. A garment order does not start there.

Forcing an ERP to do all of this means heavy customisation in the one system that most needs to stay standard. Every upgrade gets harder, the ledger fills with data finance never reads, and the merchandisers keep their spreadsheets anyway. The durable answer is to give the ERP the books and give the operations to a system built for them. Section 3 summarises that model and section 37 shows it in full.

3The recommended architecture, in short

Before discovery starts, agree which system owns which part of the business. Our recommendation is a split along the line in Example 1: SAP Business One keeps the books, and an operations system built for apparel runs everything from the style to the shipment.

With this split, the SAP Business One project stays close to standard: no variant add-on for merchandising, fewer user-defined objects, cleaner feature-package upgrades and a shorter project. The rest of this guide still explains how to bend SAP Business One toward garment production, because some factories choose to do that, and because a consultant needs to know what each choice costs. Where an area moves out of SAP Business One under the recommended model, the section ends with a short note. Section 37 describes the model in full, department by department.

4Business types, and what each needs from SAP Business One

"Apparel manufacturer" covers very different businesses, and the business type decides who owns the material, what is invoiced and which parts of SAP Business One carry weight. Settle it in the first discovery meeting, because a factory often runs two types at once, for example full package for one buyer and CMT for another.

The last three types do not manufacture at all; Part 10 covers what they need from SAP Business One and what they should leave out. The list above is general implementation practice. Treat it as a starting point for the discovery questions in section 6, not as a scope.

5Who should be on an SAP Business One apparel project team?

An apparel SAP Business One project needs one decision owner for every design question, and most of those owners sit in the factory, not in IT. The partner configures, installs add-ons and builds extensions; the factory decides how items, units, batches, costs and inspections work.

The table lists the roles we see on projects that go well. One person can hold several roles in a small factory. What matters is that every question in the fit-gap has a named person who can say yes.

Rules that keep decisions moving

Most delays in apparel projects come from decisions nobody owns. Four rules prevent them.

• One owner per decision. "Merchandising and finance will agree" produces no decision. Write one name against each fit-gap line.
• Decide in writing. Keep a decision log with the date, the owner, the option chosen and the options rejected. Discovery findings, design choices, add-on choices and change requests all go in it.
• The sponsor settles scope, not configuration. The sponsor decides whether a variant add-on is bought. The merchandising head decides how codes and sizes work in it.
• Key users are released from part of their day. A key user who is also running peak-season orders will not test properly.

6What should discovery workshops for an apparel factory cover?

Discovery for an apparel factory is one workshop per department, each walking a real, recent order from start to finish and asking where the data comes from, who changes it and what goes wrong. Use the factory's own orders, not a demo company. The polo order in this guide is the kind of order to bring.

Each workshop produces three things: the current flow as it really runs (including the spreadsheets), a list of findings mapped to the fit-gap lines in section 7, and a list of decisions with an owner. The question lists below are a starting set; add the factory's own. For SAP Business One, add one question to every workshop: how many item codes does this department touch, and how would it find them without a style grid?

Merchandising

Merchandising questions establish how orders arrive, change and are tracked.

• How does an order arrive: buyer PO by email, portal, EDI? What fields does it carry, and how often is it amended after confirmation?
• How are sizes and colours broken down, and do buyers order in ratio packs?
• How many styles, colours and sizes are active in a season, and how many item codes does that make?
• What quantity tolerance do buyers allow, and how is a short or over shipment agreed?
• Is one buyer order split into several deliveries, each with its own date and destination?
• Where is the T&A calendar kept, who updates it, and who looks at it each morning?

Development and sampling

Development questions establish what happens before an order exists.

• Which sample types does each buyer require, and in what order?
• How are sample rounds recorded: sent date, courier, comments, verdict?
• Where do tech packs live, and how is a revision after PP approval handled?
• Who prepares the quotation cost, from what inputs, and how many versions does a quote go through?

Purchasing and stores

Stores questions establish units, batches and what is measured at receipt.

• In which unit is each material bought, stocked and issued? Which suppliers invoice in a different unit from the one they deliver in?
• What is checked at receipt: weight, width, GSM, shade, shrinkage, four-point inspection? Who records it and where?
• How are dye lots and rolls labelled, and can the store find every roll of one lot today?
• Which materials are nominated by the buyer or supplied by the buyer?
• What happens to leftover fabric and trims after an order ships?

Cutting, production and subcontracting

Production questions establish the level of control and how output is counted.

• At what level is production controlled: per order, per style-colour, per size, per delivery, per cut?
• How is the cut plan made per dye lot, and who checks that lots are not mixed?
• How is output counted today: per line per hour, per operator, at end of line?
• Which processes go outside (print, embroidery, wash, CMT) and how are pieces counted out and back?
• How are rejects, repairs and second-quality pieces recorded?

Industrial engineering and planning

IE questions establish where minutes and capacity come from.

• Are operation minutes (SMV) studied per style, taken from a library, or estimated?
• How is line capacity planned across the season, including subcontractors?
• What efficiency figure is used for planning, and how is actual efficiency measured?

Quality

Quality questions establish inspections, buyer standards and who may release a failed lot.

• Which inspections run: incoming fabric, cutting, inline, end of line, pre-final, final, measurement?
• Which buyers set their own AQL levels, and where are their quality manuals kept?
• Who may release a lot that failed inspection, and is that decision logged?
• Which lab tests and certificates are required per order?

Shipping

Shipping questions establish packing rules and documents per buyer.

• How are cartons packed: solid size, assorted, ratio? What carton labels does each buyer require?
• Which export documents are prepared per shipment, and who checks them against the letter of credit?
• Does any buyer require an advance shipping notice?

Finance

Finance questions establish currencies, payment terms, import costing and tax.

• Which currencies are used for sales, purchases and wages? How are exchange differences booked today?
• How are buyers paid: letter of credit, down payment, open account? Which buyers deduct chargebacks?
• How is imported material costed: are freight, duty, clearing and bank charges added to the material cost?
• Which valuation method does the auditor expect for fabric and for finished garments?
• Is the factory in a free zone or under a temporary-admission regime, and what reports does that require?
• Which e-invoicing and tax reporting rules apply?

7The apparel fit-gap checklist for SAP Business One: 52 lines

A fit-gap checklist lists every requirement an apparel business has and records, line by line, whether SAP Business One meets it as standard, meets it with configuration, needs an add-on or custom code, or is better handled outside the ERP. The 52 lines below cover product, bill of materials and costing, materials, production, quality, sales and shipping, and finance.

The answers are our assessment of SAP Business One 10.0 for a typical full-package garment factory with no variant add-on. Where an add-on changes the answer, the notes say so. Confirm each line against your feature package and your partner's add-ons before you sign a scope.

Key: Standard works as delivered · Configure settings, user-defined fields, formatted searches or light setup · Custom build an add-on, a user-defined object or code · Operations layer better run in an apparel operations system and passed to SAP Business One

Counted from this table, 6 of the 52 lines are standard, 22 need configuration, 14 need an add-on or custom code and 10 are better run outside SAP Business One. That count is our assessment for a typical full-package factory without a variant add-on, not a survey. With a variant add-on, lines 1 and 41 usually move to configuration. A CMT factory drops most of the costing and material lines; a mill adds process lines this list does not cover.

8Which SAP Business One version, database and hosting should a garment factory choose?

SAP Business One 10.0 comes in two database versions, Microsoft SQL Server and SAP HANA, and both now run the Service Layer API, so the choice rests on the partner, the add-ons you need and the infrastructure you can run. SAP ships improvements to release 10.0 as feature packages named by year and month, such as FP 2602 and FP 2608; this chapter was checked against those.

From practice: choose the database your partner runs most often and your add-ons support best. Changing database later is a project in itself.

How much does SAP Business One cost for a garment factory?

The cost of SAP Business One for a garment factory depends on the number and type of named user licences, the database, the hosting, the add-ons and above all the partner work the fit-gap calls for. SAP Business One is sold through partners, who quote licences; we do not repeat prices here because they vary by country and change.

The fastest way to lower the total is to shrink the custom-build column. Every line moved to standard SAP Business One or to an operations system is an add-on or an extension nobody has to retest.

Questions to settle with the partner

Settle these with the partner before signing, because each changes the cost and the upgrade path.

• Which database and which feature package will go live, and when is the next feature package due?
• Which add-ons are planned, who supports them, and are they released for that feature package?
• Which extensions (user-defined objects, stored-procedure rules, integrations) are planned, and who owns their code?
• Is there a test company, refreshed from live data, for every feature package upgrade?

9SAP Business One vs Odoo for apparel

Odoo has native colour-size variants with grid entry on sales orders and a documented subcontracting flow, while SAP Business One has neither and relies on add-ons or design, but SAP Business One brings batch status, units of measure groups and an SAP ledger that many auditors and group companies prefer. Neither covers sampling, T&A, AQL or per-roll unit conversion out of the box. Odoo is an open-core ERP with a free Community edition and a licensed Enterprise edition.

Which should a garment factory choose?

Choose on the fit-gap, the partner and local compliance, not on the product name. From practice, Odoo tends to suit a factory that wants variants and subcontracting inside the ERP and has developers for Python modules; SAP Business One tends to suit a factory that values an SAP ledger and a strong inventory core and will either buy a variant add-on or keep styles in an operations system. Under the recommended model in section 37, the matrix and subcontracting gaps matter much less, because neither ERP has to hold styles. Our Odoo chapter covers Odoo in the same depth.

10SAP Business One vs NetSuite for apparel

NetSuite has matrix items, a grid order SuiteApp and an Outsourced Manufacturing feature that is the closest native match to CMT, and it is sold only as a cloud service; SAP Business One has none of those three natively but can run on your own servers or a partner's and keeps a batch-based inventory core. Oracle NetSuite is a cloud ERP; its apparel edition is the SuiteSuccess "Apparel, Footwear and Accessories" configuration.

Which should an apparel company choose?

From practice, NetSuite suits brands and wholesalers selling across channels and subsidiaries that want matrix items and a cloud service run by the vendor. SAP Business One suits factories and distributors that want an SAP ledger, local or partner hosting and a strong inventory core at a smaller scale. For a manufacturer, neither covers cutting, bundles, sampling or AQL natively. Our NetSuite chapter covers NetSuite in the same depth, and the comparison table sets all the ERPs in this guide side by side.

NetSuite and Odoo facts are from their vendors' documentation as cited in our NetSuite and Odoo chapters and in sources.

11How should item groups and materials be set up in SAP Business One for apparel?

Set up SAP Business One item groups by how each material is bought, stocked, valued and tracked: knit fabric, woven fabric, yarn, trims, packaging, subcontract services and finished garments each get their own group, because the group carries default accounts and settings for every item created in it. An item group in SAP Business One is a classification of items that supplies defaults, such as G/L accounts, to the items assigned to it. Item properties add a second classification: each item can be flagged with up to 64 properties for reporting and selection.

Apparel is not one product type. The garment category decides the size system, the main material, the unit it is bought in and the processes it goes through.

Materials, and how each is bought and used

Each material has its own purchase unit, usage unit and receipt checks, and the SAP Business One setup must follow them.

In SAP Business One, the valuation method (moving average, standard, FIFO, or serial/batch valuation for batch-managed items) is set at item level, and item groups supply defaults. Batch management is switched on per item, so switch it on for fabric, yarn and any trim that must match a dye lot, and leave it off for buttons and labels.

With operations on top: the style, its bill of materials by category and its consumption are built in the operations layer. SAP Business One still needs the item groups, valuation methods and batch settings above, because it holds stock value and the payables.

12How do you manage sizes and colours in SAP Business One without a matrix?

Standard SAP Business One has no item matrix, so each colour and size combination is its own item code, tied together by a code convention and user-defined fields for style, colour, size and season; a partner variant add-on adds the matrix on top. Partner documentation and add-on vendors state the gap plainly: there is no product variants functionality in standard SAP Business One.

A style/colour/size matrix is a grid with colours on one axis and sizes on the other, used to create items and to key order quantities for each combination. Without it, three things change for the factory:

• Item creation. Every SKU is created as an item, usually by import, not by hand.
• Order entry. A sales or purchase order has one line per SKU. The polo order is five lines; a jean in three washes is up to 63.
• Reporting by style. Sales, stock and cost by style come from grouping on user-defined fields or the item code prefix.

Three ways to hold colour and size

There are three workable designs, and the choice is made once, before any item is loaded.

Examples of variant add-ons in the SAP Business One partner market include FashionNx, iMatrix, Fashion for SAP Business One and Accelon's apparel and footwear solution. We name them only as examples that exist; we have not tested them and do not endorse any of them. Ask each vendor for its release status on your feature package and database, and for a reference customer making garments, not only selling them.

Naming and codes

Agree the code pattern before the first import and keep it short: style, colour code, size, for example P2041-NVY-L. Hold the buyer's own style number in a separate user-defined field. Keep one size field per size scale, so an "S" on a polo and an "S" on a bra band never share a value by accident. Integrations must never rely on the item code as their only link; section 34 explains why.

With operations on top: styles, colourways and size breakdowns live in the operations layer, and SAP Business One only needs the finished-goods items that are actually sold and invoiced. The factory can skip the variant add-on for merchandising entirely.

13How do you convert kilograms to metres for fabric in SAP Business One?

SAP Business One converts units through units of measure groups, and a group holds one fixed conversion that every document uses, so kg to metre for knit fabric works only as a nominal factor per fabric, not per roll. A units of measure group lists a base unit and alternative units, each with a conversion quantity to the base; in SAP's training material it is set up under Administration › Setup › Inventory › Unit of Measurement Groups.

Each item has one inventory unit, used for every stock posting, and can have several purchasing and sales units from its group. SAP's learning material adds two constraints that matter here: the inventory unit cannot be changed once transactions exist, and conversion rates inside a group cannot be changed while open documents exist for the item.

GSM means grams per square metre: the weight of one square metre of the fabric. A 180 GSM jersey weighs 180 g per square metre.

Three workable designs

There are three workable ways to hold knit fabric in SAP Business One, each with a trade-off.

Never share one group between fabrics of different weight or width. A group for "Jersey 180" is wrong for "Jersey 160" by about 12%.

With operations on top: the operations layer records a measured lot record per receipt (GSM, width, shrinkage) and works consumption in the unit the cutting room uses. SAP Business One stays in the purchase unit, kilograms, for stock value and payables, with one simple group per fabric.

14How do you track dye lots and fabric rolls in SAP Business One?

Manage fabric by batches and make each batch one dye lot; SAP Business One then asks for the batch on every receipt and issue, stores two free batch attributes, and lets a batch be held with a status of Not Accessible or Locked until it passes inspection. A dye lot is a batch of fabric dyed together; fabric from two dye lots can differ slightly in shade, so pieces cut from two lots show a colour difference once sewn into one garment.

The batch details carry the fields a fabric store needs: Batch Attribute 1 and Batch Attribute 2, expiration date, manufacturing date, admission date and location, plus the manufacturer's batch number. Rename the attributes in your forms to what they mean to you, for example "Shade group" and "Measured GSM / width".

Batch status as a quality hold

A batch has one of three statuses: Released, Not Accessible or Locked. According to SAP's knowledge base, a Not Accessible batch cannot be released in sales documents or A/P credit memos but can move by inventory transfer, and a Locked batch can be released only in inventory documents such as transfers and goods issues. The default status for new batches is set under Administration › System Initialization › General Settings › Inventory › Items. For fabric, receive new batches as Not Accessible and release each one after its incoming inspection.

Rolls

Tracking each roll is a design choice. A batch per roll gives roll-level issue and return but multiplies batches; a batch per dye lot with bin locations or serial numbers per roll keeps the dye lot as the unit. Measured width and GSM per roll need either one batch per roll or user-defined fields.

A shade band is a set of approved shade references for one fabric colour, used to judge whether a new lot is close enough to the standard. SAP Business One has no shade band object; the shade group sits in a batch attribute and the band itself lives in another system or a user-defined table.

Standard SAP Business One lets a user pick any available batch for an issue. To refuse two batches on one cut, add a validation in the SBO_SP_TransactionNotification stored procedure, which SAP Business One calls before a transaction is committed and which can roll it back with a message, or keep the cut plan in an operations system.

With operations on top: shade bands per fabric, the measured lot record and the incoming inspection that carries the dye lot sit in the operations layer. SAP Business One still holds the batch on receipts and issues, so stock value and traceability stay correct.

15How do bills of materials work for garments in SAP Business One?

SAP Business One stores bills of materials as product trees, one per parent item, so when every size is its own item, every size has its own tree and size-dependent fabric consumption is simply a different quantity on each tree. The cost is maintenance: a style in 4 colours and 5 sizes has 20 trees to keep in step. Generate them from a consumption table, never by hand.

SAP Business One offers four bill of materials types. SAP's help and learning material describe them as follows:

A production product tree lists components with quantities, and can also list resources (labour and machine time) and route stages (section 16). A sub-assembly such as an embroidered front panel is a production item with its own tree, and appears as a component in the garment's tree.

Marker efficiency is the share of the fabric in a cutting marker that ends up in garment pieces; the rest is waste between the pieces. Shrinkage is the fabric the garment loses in washing or finishing, planned into the pattern. Keep the two apart. A product tree line holds one quantity, so the factors belong in the consumption table that generates the trees, with the tree holding the result.

From practice: an edited production tree changes what the next production order copies, and open production orders keep the components they were created with. Decide who may edit trees of styles with open orders, and log each change.

With operations on top: the consumption engine (marker efficiency, shrinkage, woven construction) and the net-to-buy across the order book run in the operations layer, which passes the purchase quantity to SAP Business One. The ERP does not need a product tree per size at all.

16How do you model cutting, sewing and finishing with production orders, resources and route stages?

Model the garment's work as a production order with route stages for cutting, sewing and finishing, and put the minutes on resources that carry a cost per time unit; this gives a labour cost and a stage-by-stage view of each order, but it does not balance a sewing line. A resource in SAP Business One is a machine, a labour pool or another capacity that a production order consumes by time; a route stage is a named step in the product tree and production order that groups components and resources.

SAP Business One supports three production order types. Standard copies its components from the item's production tree; Special is for work not based on a tree, such as a repair or rework; Disassembly reports taking an item apart. An order opens as Planned, is Released for work, and is Closed when finished, which posts its variance; Planned and Released orders can be cancelled. Components are issued with Issue for Production and finished goods are recorded with Receipt from Production. SAP's how-to guide on resources and production (release 9.3) describes route stages, resource lines and production, setup and run times.

What an operation's minutes mean in a garment factory

SMV (standard minute value) is the time a trained operator needs for one operation at a normal pace, including allowances. A polo has 15 to 25 sewing operations. You can put each on the tree as a resource line, or group them per route stage. Grouping keeps production orders readable; listing every operation gives a detailed cost but floods the order.

One more design point is specific to item-per-SKU. A production order is for one item, so the polo order becomes five production orders, one per size. Cutting runs across sizes by dye lot (Example 10). Decide how the five orders are linked to one cut: a user-defined field for the cut number, or a cut plan held elsewhere.

With operations on top: the planning heat-map (lines and subcontractors, 52 weeks), production orders with job cards per department and the WIP board run in the operations layer. SAP Business One receives material issues and receipts for stock value and does not need resources or route stages.

17Where do sampling, approvals and the T&A calendar live in an SAP Business One project?

SAP Business One has no object for garment samples, buyer approvals or a T&A calendar, so a project must build them as user-defined objects, buy an add-on, or keep them in an operations system. Its approval procedures approve documents such as purchase orders, not lab dips. Before a single bulk garment is cut, the buyer approves the product in stages, each stage can take several rounds, and each approval unlocks the next step of the order.

A PP (pre-production) sample is a garment made in the actual bulk fabric and trims, which the buyer approves as the reference that bulk production must match. A T&A (time and action) calendar is the list of an order's milestones, each with a planned date worked back from the ex-factory date, an actual date and an owner.

Every round has a sent date, a courier and tracking number, the pieces sent, the buyer's comments and a verdict: approved, approved with comments, or rejected. The T&A calendar hangs on these dates.

What a user-defined sampling object must hold

SAP Business One lets a partner build new records as user-defined tables and user-defined objects, with their own forms and Service Layer endpoints. If the project builds sampling inside SAP Business One, the object needs at least these parts.

• A sample request per style and colourway, with its type (lab dip, strike-off, fit, size set, PP, TOP, shipment).
• Rounds under each request: sent date, courier, tracking number, pieces sent, buyer comments, verdict, verdict date, who recorded it.
• A link from the approved round to the spec version it approved, so a later revision cannot silently replace it.
• A block on the next step: bulk dyeing waits for the lab dip, cutting waits for the PP sample, enforced with a validation in the transaction notification procedure.
• T&A milestones that take their actual dates from the rounds instead of from someone typing them.

Because SAP Business One has no style object without an add-on, the sample request must hang on the user-defined style field, or on the add-on's style record. That is one more reason this area usually lives outside the ERP.

With operations on top: dev approvals (lab dip, strike-off, sample, shipping mark) with rounds, courier details and the buyer's verdict, the T&A calendar with its critical path, and the PP approval that locks the style version for the order all live in the operations layer. SAP Business One needs none of it.

18How does subcontracting work in SAP Business One for CMT, washing, printing and embroidery?

We found no documented standard subcontracting order in SAP Business One 10.0 in the SAP sources we checked, so apparel projects build it from standard pieces: a warehouse per subcontractor, inventory transfers to send components out, a production order for the processed item, and a purchase order for the processing charge. Some partner add-ons provide a subcontracting flow on top. Check the What's New notes of your feature package before designing, because SAP adds production features in each one.

CMT (cut, make, trim) means the factory sews garments from fabric the buyer supplies and charges only for the labour; in subcontracting, the same term describes a factory that sends cut panels to another unit to be sewn. Job work is the South Asian term for the same arrangement.

A workable pattern from practice

The pattern below is common in SAP Business One projects. It is implementation practice, not an SAP-documented feature, and each partner varies it.

1. Create a warehouse for each subcontractor, so stock at the embroiderer is visible and still valued as the factory's.
2. Create the processed item (for example "front panel, embroidered") as a production item with a tree: the cut panel plus thread, if the factory supplies it.
3. Send the cut panels with an inventory transfer to the subcontractor's warehouse, including the agreed allowance.
4. Open a production order for the processed item, issuing components from the subcontractor's warehouse.
5. When goods come back, record a receipt from production into the main warehouse for the good pieces, and account for rejects.
6. Buy the processing charge on a purchase order for a service item, so the subcontractor's invoice matches it.

Garments often visit several processors: cut panels to a printer, then to a sewing unit, then to a wash. Each step becomes its own processed item, warehouse and production order. Modelled as one step, the factory loses sight of where its goods are between processors.

Subcontractor tracking a factory expects

A factory expects to see, per processor, what went out, what came back, what was lost and whether the loss is inside the agreed allowance. SAP Business One shows stock in the subcontractor's warehouse; the allowance, reject reasons and the balance per order need user-defined fields and a report.

With operations on top: subcontract steps sit on the production order in the operations layer, and subcontractors appear on the planning heat-map beside the factory's own lines. SAP Business One receives the subcontractor's purchase order and the payable.

19How do you cost a garment in SAP Business One, and where does the garment costing sheet live?

SAP Business One values stock by a valuation method set per item (moving average, standard, FIFO, or serial/batch valuation) and adds freight, duty and other charges to receipts with a landed costs document, but the garment costing sheet used to quote a buyer is built before any item exists and usually lives outside the ERP. A garment costing sheet lists fabric, trims, making, washing, testing, freight, finance cost and margin per piece, and adds up to the price quoted to the buyer.

• Valuation method is set per item. Under serial/batch valuation, SAP describes outgoing costs as the actual incoming cost of that batch, which suits fabric bought at different prices per dye lot.
• Production variance is posted when a production order is closed, comparing what the order consumed with what it received.
• Landed costs spread freight, duty, clearing and other charges over the receipt lines.
• Multi-currency and exchange-rate differences are native, which suits selling in USD or EUR while paying costs locally.

How do you configure landed costs in SAP Business One for imported fabric and customs duties?

Define the landed cost types once (freight, clearing, bank charges, customs), each with its allocation method, then create a landed costs document from the goods receipt PO when the charges are known. A landed cost is any cost of bringing goods to the factory beyond the supplier's price: freight, insurance, customs duty, clearing and bank charges.

SAP's learning material and help describe allocation by quantity, weight, volume, equal share and cash value before customs, with customs groups holding a projected duty percentage per group of items and a broker recorded as the vendor who invoices the charges. Check the full list of allocation methods on your feature package. Choose the method per charge: sea freight follows weight or volume; clearing and bank charges usually follow value; a duty charged per kilogram follows weight. How the added cost reaches stock value depends on the item's valuation method and on whether the goods are still in stock, so test it with finance on each method you use. For a factory in a free zone or under temporary admission, duty may be zero or suspended, and the reporting rules are local; agree them with the customs broker and finance before configuring.

With operations on top: the cost engine (fabric, trims, decoration, CMT, overhead, margin to FOB, with landed cost and dated exchange rates), the standard cost sheet and quotations with approval thresholds run in the operations layer. SAP Business One holds the landed cost that actually hit the receipts, for stock value.

20Can SAP Business One run quality control and AQL inspection for garments?

Standard SAP Business One has no quality management module and no ISO 2859-1 sampling tables, so inspections are recorded in user-defined objects, a partner add-on or an operations system, while SAP Business One enforces the result through batch status and warehouses. AQL (acceptance quality limit) inspection checks a random sample drawn from a lot and accepts or rejects the whole lot according to how many defects the sample contains.

What SAP Business One does give a quality team is the hold. A fabric batch received as Not Accessible cannot go on a sales document; a Locked batch moves only on inventory documents. A quarantine warehouse gives the same effect for items without batches. Neither records what was inspected or who decided.

Quality control at cutting, stitching, dyeing and printing

A garment factory inspects at each stage where a defect is cheaper to catch than at the end. Dyeing and printing usually happen outside the factory, so those checks land on the goods coming back.

Acceptance numbers as published in ISO 2859-1 Table II-A, reproduced in common AQL references (see sources).

With operations on top: typed inspections (incoming, cutting, PP, DUPRO, final AQL, pre-shipment, measurement), the AQL engine on ISO 2859-1 at the buyer's level, CAPA, needle and metal control and quality grades (only first-quality pieces count as shippable) run in the operations layer. SAP Business One sees the delivery only once it is cleared.

21How do you handle cartons, packing lists and shipping documents in SAP Business One?

SAP Business One records packing on the delivery through its Packages window, using package types you define, and its Pick and Pack Manager moves orders from open to released to picked; buyer carton labels, SSCC numbers and pack-level packing lists usually need custom layouts. Packaging information prints on a separate page when a delivery or A/R invoice is printed, per SAP's help.

Documents a garment shipment needs

An export shipment of garments carries a standard set of documents, and a letter of credit may require each to match exactly.

With operations on top: shipments per delivery, packing and cartonisation, and ship clearance against the buyer's terms run in the operations layer. SAP Business One receives the delivery and raises the A/R invoice.

22How does SAP Business One handle multi-currency, letters of credit, down payments and chargebacks?

SAP Business One handles foreign-currency documents, exchange-rate differences, A/R down payment requests and down payment invoices, and approval procedures as standard; letters of credit and reason-coded chargebacks need design, because there is no letter-of-credit object. Garment exporters usually sell in USD or EUR, buy some materials abroad and pay wages locally, so every order touches at least two currencies.

Down payment requests and down payment invoices

SAP Business One has two documents for advances, and the difference matters to finance. An A/R down payment request asks the customer for the advance and posts no journal entry. An A/R down payment invoice records the advance to a liability account, which moves to revenue when the down payment is applied to the final A/R invoice. Choose per buyer, following local tax rules on advances.

Approval procedures

Approval procedures stop a document being added until the named approvers agree. The document is saved as a draft, sent through the approval stages, and added once approved. Use them for purchase orders above a limit, discounts beyond a limit and outgoing payments. They approve documents only; product approvals such as lab dips need another place (section 17).

Letters of credit

A letter of credit is a bank's promise to pay the exporter when documents that match the credit's terms are presented. Under ICC's UCP 600 rules, which most credits follow, documents must be presented within 21 calendar days after the shipment date unless the credit says otherwise, and never after the credit expires. SAP Business One has no LC object: the credit number, amount, latest shipment date, expiry, presentation period and required documents need a user-defined object, and a check before shipment that the documents will match.

Chargebacks

A chargeback is an amount a buyer deducts from a payment for a claimed failure: a late shipment, a wrong carton label, a missing or wrong advance shipping notice. It arrives as a short payment. Record the shortfall against a chargeback account per reason, or with a reason user-defined field on the credit memo, and keep the buyer's deduction notice attached. Without reason codes, nobody can tell whether the factory loses money to labels or to lateness.

With operations on top: finance stays in SAP Business One in full. The operations layer sends the orders, deliveries and purchase requests that the invoices and payables are built on; no money amounts travel through its ERP API.

23Does SAP Business One support e-invoicing and localisation for garment-exporting countries?

SAP releases SAP Business One with country localisations, and local tax, reporting and e-invoicing depend on the localisation for your country and on your partner; we have not verified e-invoicing coverage for any specific garment-exporting country in this chapter. E-invoicing rules change often, so treat any statement older than the current tax year with care.

Turkey, Egypt, Pakistan, Bangladesh, India, Vietnam, Morocco, Tunisia and others each have their own invoicing, VAT and export-incentive rules. Check SAP's list of localisations for release 10.0, ask the partner which statutory reports and e-invoicing connections they have delivered in your country, and test an e-invoice end to end in a test company before go-live.

Factories in free zones or under temporary admission often report the import and re-export of materials to customs. SAP Business One stock movements and batches carry the quantities, but the report format is local and usually custom.

24In what order should you configure SAP Business One for a garment factory?

Configure SAP Business One for a garment factory from the ledger outward: company, chart of accounts, currencies and taxes first, then units of measure groups, batch settings, item groups and valuation, then warehouses, then production and approvals, and only then the items and product trees. Each step depends on the one before it; loading items before their units and groups are final means reloading them, and an item's inventory unit cannot be changed once it has transactions.

Menu paths change between releases and between the desktop client and the Web Client. The table names the area and gives a path only where we confirmed it in SAP material; check every path on your feature package.

Two item-level switches complete the setup: fabric items are managed by batches, and each finished item's procurement method is set to make, so MRP recommends production orders rather than purchase orders for it. Both are easier to set in the import file than by hand.

25How do you extend SAP Business One for apparel: user-defined fields, objects, add-ons and the SDK?

SAP Business One is extended with user-defined fields on existing records, user-defined tables and objects for new records, validation rules in the transaction notification stored procedure, and add-ons built on the SDK (the DI API for data, the UI API for screens) or bought from partners. Every extension must be retested at each feature package, so keep the list short and owned.

Which extensions an apparel project usually needs

An SAP Business One apparel project that keeps operations inside the ERP usually needs most of the list below. The names are descriptive, not real packages. Look for a maintained add-on before building, and check each against your feature package.

Every row is an add-on to license or code someone must retest at each feature package. That is the real cost of keeping operations inside SAP Business One, and it recurs.

26Which systems does an SAP Business One apparel implementation integrate with?

An SAP Business One apparel implementation typically connects to a PLM or tech-pack system, a shop-floor system, EDI with retailers, banks and an operations layer, through the Service Layer, the DI API or the integration framework (B1if); each connection needs one owner per field and links stored on permanent keys. The table shows the usual source of truth for each kind of record, based on general practice.

The integration framework for SAP Business One (B1if) is SAP's tool for message-based scenarios: transformation, routing and monitoring between SAP Business One and other systems. From practice, partners use it where a connection needs mapping or several companies, and the Service Layer for direct web and cloud integrations.

Rules for every connection

Four rules prevent most integration faults, whether the other side is a PLM, a floor system or an operations layer.

• Link on DocEntry or the item code you control, never on a document number (DocNum) a numbering series can change or a text field users edit.
• One writer per field. If two systems can change the same quantity, one of them is wrong without knowing it.
• Show disagreements to a person. When the other system says something different, put it on a review list; never overwrite silently.
• Make receivers safe to call twice, so a retried message does not create a second purchase order. SAP's own webhook guide says retries can deliver duplicates.

27How do you migrate apparel data into SAP Business One?

Migrate only open and active apparel data into SAP Business One (active SKUs, open orders, open purchase orders and stock by batch), load it with the Data Transfer Workbench in dependency order, and have each department head sign off the loaded figures. The Data Transfer Workbench (DTW) is SAP's tool for importing data from CSV files into SAP Business One; it ships with templates for each business object, arranged like the main menu, and user-defined objects can be imported with customised templates.

Load order

Each object depends on the ones above it. Load and check each level before starting the next.

The cut-off rule

A cut-off rule states the exact moment after which every transaction is entered in SAP Business One and not in the old system. Write it as a date and time, name what happens to documents in flight (a truck at the gate, an inspection half done), and stop receiving into the old system at that moment. Stock is counted at the cut-off and loaded as it was counted, batch by batch, not as the old system said.

Cleansing

Clean data before it is loaded, never after. The usual work in an apparel migration is listed below.

• Merge duplicate suppliers and materials ("Navy Jersey 180", "Jersey 180 NVY").
• Retire styles with no order in two seasons, so their SKUs are never created.
• Give every fabric one units of measure group, and every roll in stock its batch.
• Map old size labels to the new valid values, one scale at a time.
• Split any "open" order line that is already partly delivered into delivered and open quantities.

ItemCode,ItemName,ItemsGroup,U_Style,U_Colour,U_Size,U_Season
P2041-NVY-S,Men's piqué polo P-2041 Navy S,Finished garments,P-2041,NVY,S,AW26
P2041-NVY-M,Men's piqué polo P-2041 Navy M,Finished garments,P-2041,NVY,M,AW26
P2041-NVY-L,Men's piqué polo P-2041 Navy L,Finished garments,P-2041,NVY,L,AW26
P2041-NVY-XL,Men's piqué polo P-2041 Navy XL,Finished garments,P-2041,NVY,XL,AW26
P2041-NVY-XXL,Men's piqué polo P-2041 Navy XXL,Finished garments,P-2041,NVY,XXL,AW26

Order,ItemCode,Quantity,Price,LineTotal
SO-P2041,P2041-NVY-S,300,4.26,1278.00
SO-P2041,P2041-NVY-M,750,4.26,3195.00
SO-P2041,P2041-NVY-L,900,4.26,3834.00
SO-P2041,P2041-NVY-XL,750,4.26,3195.00
SO-P2041,P2041-NVY-XXL,300,4.26,1278.00

Open PO:  navy jersey 180 GSM, 925 kg ordered, 0 kg received
Stock:    buttons 15 mm navy, 9,504 pcs (66 gross), main warehouse, no batch

Sign-off

Each owner signs a one-page check of their data: record counts against the old system, totals (stock value, open order value, open payables) and five records picked at random and checked on screen. A migration with no signatures is a migration nobody owns when the first figure is wrong.

28How should you test an SAP Business One apparel implementation end to end?

Test an SAP Business One apparel implementation with end-to-end scenarios that follow one real order from the buyer's PO to cash, run by the factory's key users in a test company copied from migrated data, each step with an expected result written down before the test starts. Testing screens one by one proves the configuration works; only end-to-end scenarios prove the business works.

The 13 scenarios below cover the flows where apparel projects usually break. Run each at least twice: once by the partner to find faults, once by the key users to accept the result. Run them again after every feature package upgrade.

Test script: subcontract embroidery with loss

Scenario T5 proves that panels sent out, panels returned and panels lost add up. The polo's chest logo is embroidered outside, with a 1% allowance, using the pattern in section 18.

Test script: short shipment within tolerance

Scenario T6 proves that a short shipment inside the buyer's tolerance is invoiced on what shipped. The buyer allows ±3%; the factory ships 2,940 pieces, 30 short in M and 30 short in L.

Step 4 of T6 needs the tolerance rule from section 25; standard SAP Business One has no quantity-tolerance field on a sales order.

29How should you train a garment factory's staff on SAP Business One?

Train each role only on the windows and scenarios it will use, in the local language, on the factory's own items and orders, and have key users teach their colleagues. A merchandiser does not need the financial menus, and a floor supervisor needs one screen that works, not an introduction to SAP Business One.

Train close to go-live, so that what people learn is still fresh, but not so close that there is no time to repeat a session. Keep each session short and practical: people learn by entering an order they recognise. The plan below is an example for the polo factory; hours are practice, not a standard.

Floor operators and supervisors are trained on whatever captures floor output. If that is a kiosk or scanner screen, the training is minutes, not hours; if it is the SAP Business One desktop client, expect the data never to arrive.

30What does an SAP Business One cut-over plan look like for a garment factory?

An SAP Business One cut-over plan is a day-by-day list of the steps that move the factory from the old system to SAP Business One: freeze, final DTW loads, stock count by batch, opening balances, checks and the first live transactions, each with an owner and a go or no-go point. Rehearse it once in full in a test company before the real weekend.

31When should a garment factory go live on SAP Business One, and how long is hypercare?

Go live between seasons, in the lowest-volume weeks and before a new wave of cutting starts, and keep the partner in close support until at least the first month-end close is done in SAP Business One. Hypercare is the period right after go-live when the project team stays on hand to fix issues daily.

• Timing. Avoid the weeks before a main shipment window, the financial year-end and any audit. A go-live in peak season turns every small fault into a missed shipment.
• Feature packages. Do not apply a new feature package in the first weeks after go-live; plan it after hypercare, with the test scripts ready.
• Parallel running. A short, bounded parallel run of the books can help finance compare figures. Running the whole factory in two systems rarely works, because people keep using the one they trust.
• Duration. Practitioners commonly plan hypercare of four to eight weeks. That range is judgement, not a measured standard; the rule that matters is that nobody leaves before the first month-end close in SAP Business One is complete.
• Issue log. Keep one list: date, who, what happened, severity, owner, status. Review it daily in the first two weeks.
• Exit criteria. Hypercare ends when the month-end closes on time, no issue blocks shipping or invoicing, and key users handle first-line questions without the partner.

32What are the most common mistakes when implementing SAP Business One for apparel?

The most common mistakes in apparel SAP Business One projects are deciding the variant approach too late, creating every colour-size combination as an item, one units of measure group shared by different fabrics, dye lots not enforced at issue, and assuming a standard subcontracting order exists. The list below comes from implementation practice, not from SAP's documentation.

1. The variant add-on decided after master data.Items loaded one way must be reloaded the add-on's way; decide before the first import and budget the add-on's upgrades per feature package.
2. Every combination created as an item.Thousands of SKUs and product trees nobody sells or maintains.
3. One units of measure group for several fabrics.Stock in metres looks right while the cutting room runs short; and the factor cannot change while documents are open.
4. One product tree copied to every size.Large sizes run short and small sizes leave surplus (Example 11).
5. Batches not enforced at issue.Shade differences are found at final inspection instead of at cutting.
6. Batches received as Released.Fabric is issued before its inspection; receive as Not Accessible and release deliberately.
7. The production order used as the production plan.Line balancing, operation times and bundle flow need their own place.
8. Subcontracting assumed to be standard.Goods disappear between processors when the transfer pattern is not designed.
9. Too much logic in the transaction notification procedure.One unreviewed stored procedure blocks documents across the company after a feature package; keep rules small, commented and tested.
10. Integrations linked on document numbers.A numbering series change breaks every link; link on DocEntry.
11. Add-ons not checked against the feature package.An upgrade waits for the slowest add-on vendor.

The 15 general failure modes, and how each shows up in SAP Business One

Apparel ERP projects fail in the same fifteen ways whatever the ERP. The table maps each one to where it appears in an SAP Business One project and how to prevent it.

33What must be decided before an SAP Business One apparel go-live?

Decide the variant approach, the item code convention, the units of measure group for every fabric, the batch rules, the valuation method per item group, the database and hosting, and which system owns sampling, T&A and floor capture before go-live, because each is expensive to change once transactions exist. The full list:

• Variant approach: item per SKU, a named variant add-on, or styles in an operations layer.
• Item code convention and the user-defined fields that group SKUs into styles.
• When a colour-size combination becomes an item.
• The units of measure group and inventory unit for every fabric and yarn.
• Batch per dye lot or per roll; what goes in Batch Attribute 1 and 2; the default batch status.
• Valuation method per item group, and which receipts take landed costs by which allocation.
• Database (SQL Server or SAP HANA), feature package and hosting.
• Which rules live in the transaction notification procedure, and who owns that code.
• Which system owns sampling, T&A, planning, floor capture and quality: SAP Business One, add-ons or an operations layer.
• How buyer-supplied fabric is held so it never enters stock value.
• The quantity tolerance rule and who may approve a shipment outside it.
• How profitability per order is tagged: projects or dimensions.
• Which API the integrations use, and on which keys they link.

34Which SAP Business One API should an apparel integration use: Service Layer or DI API?

Build new web and cloud integrations on the SAP Business One Service Layer, which speaks OData over HTTPS on both the SQL Server and SAP HANA versions, and keep the DI API for add-ons installed on Windows alongside the desktop client. SAP's Service Layer guide describes it as built on the same core as the DI API, reusing its metadata, so the business objects and their properties match.

How the Service Layer works

The facts below are from SAP's guide "Working with SAP Business One Service Layer" (document version 1.29, July 2026) and its API reference for release 10.0.

• Log in, keep the cookie. POST /Login under the Service Layer base URL (SAP's example is https://<server>:50000/b1s/v1/Login) with CompanyDB, UserName and Password returns a B1SESSION cookie, sent on every later request, and a ROUTEID cookie for load-balancer stickiness. The response includes a SessionTimeout value (30 in SAP's example). Use a dedicated integration user with only the authorisations it needs. As of FP 2305, a Windows domain account can also log in once Active Directory is set up.
• Page through lists. The default page size is 20. Send Prefer: odata.maxpagesize=100 or follow the next link in each response.
• Protect updates. As of FP 2102, documents including PurchaseOrders, PurchaseRequests, PurchaseDeliveryNotes, Orders, Items and BusinessPartners carry ETags; send If-Match so an update fails with 412 if someone changed the record in between.
• Group calls. $batch sends several operations in one request.
• Read with SQL where needed. As of FP 2011, SQLQueries runs saved SQL through the Service Layer on both databases.
• Listen for changes. As of FP 2602, webhooks: enable them per company, create an EventSubscriptions record naming the business object and transaction type, and run the Webhook Messenger Service. SAP's FAQ says a failed notification is retried up to five times (2, 4, 8, 16 and 32 seconds), that retries can produce duplicates, and that receivers should be idempotent.
• Extend. User-defined fields appear with a U_ prefix; user-defined tables and objects get their own endpoints.

Which objects does an apparel integration use?

These entity sets appear in SAP's Service Layer API reference for release 10.0: Items, BusinessPartners, Orders, PurchaseRequests, PurchaseOrders, PurchaseDeliveryNotes (goods receipt PO), InventoryGenExits (goods issue), ProductionOrders, ProductTrees, LandedCosts, BatchNumberDetails, SerialNumberDetails, UnitOfMeasurementGroups, Resources and UserFieldsMD. Confirm field names in your own $metadata before mapping, because feature packages add fields.

Which key should the link be stored on?

Store every link on DocEntry, the document's internal key, which the Service Layer uses in its URLs (for example /PurchaseOrders(1187)). DocNum is the number people read, taken from a numbering series; show it, never link on it. For items, the item code is the key; agree with the factory that item codes are never renamed.

Push or pull?

On FP 2602 or later, subscribe to webhooks for the objects you care about, and keep a scheduled pull as the safety net for anything missed while the receiver was down (SAP also documents a replay for missed events). On earlier feature packages, pull on a schedule, filtering on the documents' update date and reading changes since the last successful run.

POST /b1s/v2/PurchaseOrders
Cookie: B1SESSION=…; ROUTEID=.node1

{"CardCode": "V-MILL01",
 "DocDueDate": "2026-11-05",
 "U_MOS_Request": "PR-1042",
 "DocumentLines": [{"ItemCode": "FAB-JER180-NVY",
                    "Quantity": 925,
                    "WarehouseCode": "01"}]}

→ 201 Created  {"DocEntry": 1187, "DocNum": 457,
                "DocumentStatus": "bost_Open", …}

POST /api/v1/erp/po-status
Idempotency-Key: sapb1-po-1187-open

{"rows": [{"request_ref": "PR-1042",
           "erp_po_id": "1187",
           "erp_po_number": "457",
           "status": "Open",
           "date": "2026-10-21"}]}

35Is SAP Business One a good ERP for fashion brands, buying agents and own-label retailers?

SAP Business One can be a good ERP for a fashion or clothing brand, a buying house or an own-label retailer, provided it is used for what they transact (purchase orders to factories, landed cost, vendor payments, wholesale sales and commission invoices) and the manufacturing modules are left switched off. The work that decides whether their orders arrive on time happens at factories they do not own, and SAP Business One has no object for most of it.

Who they are

Three kinds of apparel business never cut a garment themselves, and each uses an ERP differently.

What a brand or own-label retailer needs from SAP Business One

An ERP for fashion brands, and an ERP for clothing brands that sell wholesale, is a buying, stock and selling ledger. In SAP Business One that means these standard documents and functions.

• Purchase orders to factories, one line per SKU item, FOB or CMT, with approval procedures above a limit. On CMT, the brand also buys the fabric and sends it to the factory, so the subcontractor-warehouse pattern in section 18 applies.
• Landed costs for freight, insurance, duty and clearing on each goods receipt PO, so stock carries its real cost.
• Vendor payments and advances: A/P down payments to factories and outgoing payments; letters of credit as a user-defined object.
• Wholesale sales orders, deliveries and A/R invoices to retailers, with packages on the delivery.
• EDI 850, 856 and 810 with retailers, through an EDI provider or add-on, often via B1if; and reason-coded chargebacks when retailers pay short (section 22).
• Multi-currency: factories invoice in USD, customers pay in EUR or GBP, the books sit in local currency.

What a buying agent needs from SAP Business One

A buying house ERP is mostly an accounting system. The agent holds no stock and has no goods payables or receivables; its income is a commission invoice to the buyer, raised as an A/R invoice for a service. SAP Business One marketing documents can be item-based or service-based, so the agent can invoice commission without creating stock items. Multi-currency matters, because commission is often invoiced in the buyer's currency.

How a buying agent's commission flows

An agent's commission is earned on the orders it places, and the design question is when the income is recognised and who owes it. Settle three points with finance before configuring.

• Who pays. Most buying houses invoice the buyer (the brand or retailer) for a percentage of FOB. Some are paid by the factory instead; then the invoice goes to the factory, and the buyer may never see it. Each principal is a customer business partner in SAP Business One.
• When it is invoiced. On order confirmation, on shipment, or on the buyer's payment to the factory. Invoicing on shipment is common because the shipped quantity, not the ordered quantity, sets the amount.
• Which rate and currency. Rates differ by buyer and sometimes by product. Hold the agreed rate on the business partner in a user-defined field, and invoice in the currency the agreement names.

The shipped quantity that drives the invoice comes from outside SAP Business One, because the agent does not receive or ship the goods. That is the gap an operations system fills: it knows which factory shipped which order and when, and the agent's SAP Business One raises the invoice from it.

A set-up list for a brand on SAP Business One

A brand or own-label retailer can go live with a smaller configuration than a factory. The list below is the core, in the order a partner would build it.

• Chart of accounts, currencies and taxes, including import duty and VAT on imports.
• Business partners: factories and mills as suppliers, retailers and marketplaces as customers, forwarders and brokers as suppliers of services.
• SKU items with the style, colour, size and season fields from section 12, or a variant add-on if merchandisers key grid orders into SAP Business One.
• Units of measure groups for pieces, packs and cartons.
• Landed cost types for freight, insurance, duty and clearing, and customs groups with projected duty.
• Approval templates for factory purchase orders above a limit.
• A/P down payments for factories that ask for advances, and a user-defined object for import letters of credit.
• Sales documents, package types and EDI for each retailer that requires it, with reason-coded chargebacks.

For an own-label retailer, the same list applies up to the warehouse. What happens after it (store replenishment, allocation, point of sale) belongs to a retail system.

What to skip

A brand, agent or own-label retailer should not buy or configure the manufacturing side: product trees, production orders, resources, route stages and MRP for production. A brand that holds stock still needs item groups, batches only where its buyers demand lot traceability, units of measure groups for cartons and packs, and valuation methods. An agent needs almost nothing from inventory.

36Where does SAP Business One stop for brands and agents, and what runs on top?

SAP Business One stops at the factory gate: it records the purchase order and the goods receipt, but not the development, sampling, T&A, production follow-up and vendor inspections that happen at the factory in between. For a brand or a buying agent, that middle is the job. This is where sourcing agent software and private label sourcing tools earn their place.

In practice, brands and agents fill this gap with a tracking spreadsheet per buyer, email threads per factory and inspection reports as PDF attachments. The cost shows up late: a lab dip approved in an email nobody forwarded, a PP sample still at the courier when cutting was due, an inspection failed at the vendor after the vessel was booked. None of these is a finance event, so none of them reaches SAP Business One until it becomes a late goods receipt or a chargeback.

Customising SAP Business One to hold this work means user-defined objects for styles, samples, milestones and inspections, each linked to purchase orders across many factories, and a portal for the factories to update them. That is a second system built inside the first. For a buying house, where this follow-up is the whole service it sells, a sourcing tool built for it is usually the cheaper route.

The MerchandiserOS model for brands and agents

Under the same split as the rest of this guide, MerchandiserOS runs development, samples and approvals, the T&A calendar, the orders placed with factories, sourcing, the planning view across subcontracted factories, quality inspections and shipping follow-up. SAP Business One keeps the books: purchase orders as the financial record, payables, landed cost, stock value, sales invoices, commission invoices and payments. MerchandiserOS includes workspace set-ups for a Brand and for a Buying agent. Retail back-office work (stores, point of sale, allocation and open-to-buy) is outside MerchandiserOS's scope; a retailer keeps its retail system for that.

·Glossary of apparel and SAP Business One terms

Short definitions of the apparel and SAP Business One terms used in this guide.

AQL

Acceptance quality limit: an inspection method that checks a random sample from a lot and accepts or rejects the lot on the number of defects found, using ISO 2859-1 tables.

Batch

In SAP Business One, a quantity of an item received together and tracked under one number; used here for a dye lot.

Batch status

Released, Not Accessible or Locked: controls which documents can use a batch.

B1if

The integration framework for SAP Business One, used for message-based integration with transformation, routing and monitoring.

CM, CMT

Cut and make, or cut, make and trim: the labour charge for making a garment, and a factory model where the buyer supplies the fabric and the factory charges only for making.

Colourway

One colour version of a style, with its own fabric shade and trims.

Cut-over

The planned switch from the old system to SAP Business One, around a fixed cut-off moment.

DI API

The Data Interface API: SAP Business One's COM library for reading and writing data, used by add-ons.

DocEntry, DocNum

A document's internal key, and the number people read from a numbering series. Integrations link on DocEntry.

Down payment invoice

An A/R document that records an advance to a liability account until it is applied to the final invoice.

DTW

Data Transfer Workbench: SAP's tool for importing CSV data into SAP Business One.

DUPRO

During-production inspection, done once part of the order is packed.

Dye lot

A batch of fabric dyed together; pieces from different dye lots can differ in shade and must not be mixed in one garment.

Ex-factory

The date goods leave the factory for shipment.

Feature package (FP)

A release of improvements to SAP Business One 10.0, named by year and month, such as FP 2602.

FOB

Free on board: the price of goods loaded at the port of shipment; in garment trade, the usual quoted price per piece.

GSM

Grams per square metre: the weight of fabric.

Hypercare

The period after go-live when the project team fixes issues daily.

Item group

A classification of items in SAP Business One that supplies defaults such as accounts.

Lab dip

A small dyed fabric sample sent to the buyer to approve a shade before bulk dyeing.

Landed cost

Every cost of bringing goods to the factory beyond the supplier's price: freight, insurance, duty, clearing, bank charges.

Letter of credit (LC)

A bank's promise to pay an exporter when documents matching the credit's terms are presented.

Marker efficiency

The share of fabric in a cutting marker that ends up in garment pieces.

POM

Points of measure: the garment measurements in a tech pack, with a tolerance per size.

PP sample

Pre-production sample: a garment in bulk fabric and trims that the buyer approves as the reference for production.

Product tree

SAP Business One's bill of materials, of type Production, Sales, Assembly or Template.

Ratio pack

A pack or carton holding sizes in a fixed ratio, for example 1 S, 2 M, 2 L, 1 XL.

Resource

In SAP Business One, a machine, labour pool or other capacity used by a production order, with a cost per time unit.

Route stage

A named step in a product tree and production order, such as cutting, sewing or finishing.

Service Layer

SAP Business One's OData web API, at /b1s/v1 (OData version 3) and /b1s/v2 (OData version 4).

Shade band

A set of approved shade references for a fabric colour, used to judge each new lot.

SMV

Standard minute value: the time a trained operator needs for one operation at a normal pace.

Size/colour matrix

A grid of colours by sizes used to create items and enter order quantities for each combination.

Strike-off

A sample of a print or embroidery on the actual fabric, approved before bulk.

T&A calendar

Time and action calendar: an order's milestones with planned dates worked back from ex-factory, actual dates and owners.

TOP sample

Top of production: the first bulk pieces, checked against the PP sample.

Transaction notification

The SBO_SP_TransactionNotification stored procedure, which can refuse a document before it is committed.

UCP 600

The ICC's rules for documentary credits, which most letters of credit follow.

Units of measure group

In SAP Business One, a base unit and alternative units with fixed conversions, assigned to items.

User-defined field, table, object

SAP Business One's ways to add fields to existing records and to add new records with their own forms.

·Checklists: an SAP Business One apparel implementation on one page

The checklists below repeat the decisions and checks from each part of this guide, in project order. The methodology page explains the method behind them for any ERP.

Discovery

Discovery is complete when every item below is ticked.

• Business type settled for each buyer: CMT, full package, or both; or brand, agent or own-label retailer.
• One decision owner named for each area.
• One workshop per department, walking a real recent order.
• All 52 fit-gap lines answered with evidence, decision and owner.
• Architecture decided: what SAP Business One owns, what runs in an operations layer.
• Variant approach, database, feature package, hosting and add-ons confirmed against the fit-gap.

Design

Design is complete when every item below is decided and written down.

• Item groups with valuation method; landed cost types with allocation methods.
• Item code convention and user-defined fields for style, colour, size and season.
• A units of measure group per fabric, with the inventory unit fixed.
• Batch = dye lot; batch attributes defined; default batch status Not Accessible.
• Size consumption source decided, and how product trees are generated.
• Route stages, resources and minutes; what stays in planning outside SAP Business One.
• Subcontract pattern: warehouses, processed items and service purchase orders.
• Inspection points, AQL plan source and override rights.
• Package types, carton rules and buyer documents per buyer.
• Currencies, down payments, LC records, chargeback reasons, e-invoicing.

Build, data and testing

Build, migration and testing are complete when every item below is proven on the go-live feature package.

• Configuration done in dependency order, on the go-live feature package.
• Extensions and add-ons listed with owners; transaction notification rules reviewed and commented.
• Integrations link on DocEntry, with one writer per field.
• Migration loaded with DTW in order, with a cut-off rule and signed totals.
• All 13 end-to-end scenarios passed by key users.

Go-live

Go-live is ready when every item below is in place.

• Training done per role, on the factory's own orders.
• Cut-over rehearsed once in full in a test company.
• Go-live date between seasons, away from year-end and audits.
• Go or no-go point and fall-back defined.
• Hypercare runs at least until the first month-end close in SAP Business One.

·Sources

SAP pages and documents were checked on 26 September 2026 against SAP Business One 10.0. Where a fact rests on a partner or community source rather than SAP's own documentation, the text says so.

1. SAP, Working with SAP Business One Service Layer (document version 1.29, 2026-07-27): OData versions, login and session, paging, ETags, $batch, SQLQueries, webhooks from FP 2602, user-defined fields and objects, Service Layer and DI API — help.sap.com
2. SAP, Service Layer API Reference, release 10.0 (entity sets) — help.sap.com
3. SAP Help Portal, Consuming SAP Business One Service Layer — help.sap.com
4. SAP, Platform Support Matrix SAP Business One (document version 1.39, 2026-08-28) — help.sap.com
5. SAP Help Portal, Bill of Materials Types — help.sap.com · SAP Learning, Utilizing Bill of Materials in SAP Business One — learning.sap.com
6. SAP Learning, Working with Units of Measure in SAP Business One — learning.sap.com · SAP consultant training, units of measure (menu path) — help.sap.com
7. SAP Learning, Exploring the Inventory Valuation Methods in SAP Business One — learning.sap.com · SAP, How to Set Up and Use Serial/Batch Valuation Method (10.0) — help.sap.com
8. SAP Help Portal, Batch Details window — help.sap.com · SAP Knowledge Base Article 3423633, Batch Status: Released, Not Accessible, Locked — support.sap.com
9. SAP Help Portal, Item Properties setup — help.sap.com · Item Groups setup — help.sap.com
10. SAP, How to Work with Resources and Production in SAP Business One (9.3) — help.sap.com · SAP Learning, Running the Production Process in SAP Business One — learning.sap.com
11. SAP Learning, Exploring the Materials Requirements Planning (MRP) Process — learning.sap.com
12. SAP Help Portal, Landed Costs setup — help.sap.com · SAP Learning, Managing Landed Costs During the Import Process — learning.sap.com
13. SAP Help Portal, A/R Down Payment Invoice — help.sap.com · A/R Down Payment Invoices Process — help.sap.com
14. SAP Learning, Implementing the Approval Processes in SAP Business One — learning.sap.com
15. SAP Help Portal, Pick and Pack windows — help.sap.com
16. SAP Help Portal, Data Transfer Workbench for SAP Business One — help.sap.com
17. SAP Help Portal, Integration framework for SAP Business One — help.sap.com · SAP Business One SDK help center (DI API, UI API) — help.sap.com
18. SAP, How to Package and Deploy SAP Business One Extensions for Lightweight Deployment (10.0) — help.sap.com
19. SAP Community, The SP_TransactionNotification stored procedure — community.sap.com
20. SAP Community, updating production orders and approving purchase requests via the Service Layer — community.sap.com · community.sap.com
21. SAP Help Portal, What's New in 10.0 FP 2602 — help.sap.com · SAP Business One Blog, FP 2608 new features (partner) — sap-b1-blog.com
22. Service Layer v1 and v2 (partner glossary) — sap-b1-blog.com · Web Client on both databases (partner) — vision33.com
23. No standard item variants in SAP Business One (partner documentation) — sana-commerce.com · emerging-alliance.com
24. Variant add-ons named as examples only — FashionNx wmsspl.com · iMatrix citixsys.com · Fashion for SAP Business One sap-b1-blog.com · Accelon accelontech.com
25. Oracle NetSuite documentation: matrix items — oracle.com · Grid Order Management — oracle.com · Outsourced Manufacturing — oracle.com · costing methods — oracle.com
26. Odoo documentation: product variants (18) — odoo.com · subcontracting resupply (18) — odoo.com · units of measure (19) — odoo.com · JSON-2 API (19) — odoo.com
27. ISO 2859-1, Sampling procedures for inspection by attributes — iso.org
28. AQL tables and acceptance numbers — qima.com · tetrainspection.com · inspection levels: qualityinspection.org
29. UCP 600, documentary credits — uscib.org · tradefinanceglobal.com
30. EDI transaction sets — 1edisource.com · celigo.com

Corrections. SAP Business One changes with each feature package, and a menu path, an API field or a feature boundary can move in a single release. If you find a statement here that your release contradicts, report a correction with the feature package and the page you checked; we correct the guide and note the change and its date at the top of this section. We re-check the SAP Business One facts in this chapter at least once a year and after each major feature package. Related chapters: Odoo, NetSuite, SAP S/4HANA for fashion and Dynamics 365 Business Central.

SAP, SAP Business One and SAP HANA are trademarks or registered trademarks of SAP SE, used here only to name the products. This guide is not endorsed by SAP SE. Microsoft SQL Server is a trademark of Microsoft. Oracle NetSuite, Odoo, FashionNx, iMatrix and Accelon are trademarks of their owners. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.