How to Implement SAP S/4HANA for Fashion for Garment & Apparel Business (2026 Guide)

1Who SAP S/4HANA for fashion and vertical business fits

SAP S/4HANA for fashion and vertical business fits multinational fashion brands, vertical manufacturer-retailers and groups that sell through wholesale, retail and e-commerce at the same time and need to allocate one stock across those channels. It is SAP's industry solution for fashion on S/4HANA, built on the same base as SAP S/4HANA Retail, and it replaces the two ECC-era solutions, SAP Apparel and Footwear (AFS) and SAP Fashion Management.

SAP S/4HANA for fashion and vertical business is SAP's fashion industry solution on the S/4HANA core, covering style-colour-size articles, seasons, segmentation, allocation and fashion manufacturing in one system. The product first shipped with S/4HANA 1709 in September 2017, and wholesale and manufacturing were added with feature pack stack 02 (FPS02), according to SAP's own community introduction and partner write-ups (sources). Before it, apparel companies on SAP ran the AFS add-on on R/3 and ECC, or SAP Fashion Management on ECC.

It suits a business with the scale, the budget and the in-house SAP team to run a large ERP. It suits a small single-site garment factory less well: the licence, the implementation partner and the internal SAP skills are sized for groups, and many of its strongest features (multi-channel allocation, segmentation by channel, supply assignment) solve a brand's problem more than a factory's. Factories with SAP ambitions but a small office often look at SAP Business One with an apparel add-on instead (section 9).

Signs S/4HANA for fashion is a good choice

S/4HANA for fashion tends to work when the business already thinks in channels, seasons and allocation, and has people to run SAP.

• The company sells the same styles through several channels and fights over who gets scarce stock. Segmentation and supply assignment exist for exactly this (section 12, section 22).
• It already runs SAP AFS or SAP Fashion Management and must move before its maintenance ends (section 8).
• It has, or will fund, an SAP competence centre: functional leads for sales, purchasing, production, quality and finance, and a Basis and integration team.
• Group reporting, multiple company codes and several countries must sit in one ledger.

Signs to slow down

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

• The factory expects SAP to hold the tech pack, the graded measurements and every sample round. That is PLM or operations work (section 27).
• The factory expects SAP production orders to balance sewing lines hour by hour.
• The team plans to lift the AFS grid design one to one into S/4HANA. The article model is different, and a straight copy repeats every old problem (section 28).
• Nobody has checked which fashion scope items the chosen edition actually contains.

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 built a fashion industry solution precisely because its core met this wall, and even that solution leaves development, sampling and the sewing floor largely to other systems. The same wall stands in front of brands, buying agents and own-label retailers: their styles, samples and orders also exist long before anything is bought or sold, only at someone else's factory.

An ERP is built around the transaction: a known article, 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. In SAP that cost is sharper than elsewhere, because modifications to the core make every release upgrade harder, and SAP's current guidance pushes extensions out of the core (section 26). The durable answer is to give SAP 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 keeps the books, and an operations system built for apparel runs everything from the style to the shipment.

For a brand or a vertical retailer, SAP often keeps more than the books: the retail and wholesale sales, allocation and distribution-centre stock that S/4HANA for fashion was built for. The split still holds for the factory side of the business. The rest of this guide explains how to bend S/4HANA toward garment production, because some companies choose to, and because a consultant needs to know what each choice costs. Where an area moves out of SAP under the recommended model, the section ends with a short note. Section 36 describes the model in full.

4Business types, and what each needs from S/4HANA for fashion

"Apparel manufacturer" covers very different businesses, and S/4HANA for fashion was designed first for the brand and retail end of them. The business type decides who owns the material, what is invoiced and which parts of SAP carry weight. Settle it in the first discovery meeting, because a group often runs two types at once.

Brands, buying agents and own-label retailers that do not manufacture have their own part in this guide (section 36). 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 S/4HANA fashion project team?

An S/4HANA fashion project needs one decision owner for every design question, and most of those owners sit in the business, not in IT. The implementation partner configures and builds; the business decides how articles, seasons, segments, units, batches, costs and inspections work.

The table lists the roles we see on projects that go well. SAP projects add roles a smaller ERP does not need: a solution architect who owns the article and segmentation model, and a Basis and integration lead. One person can hold several business roles in a smaller company. What matters is that every fit-gap line has a named person who can say yes.

Rules that keep decisions moving

Most delays in apparel projects come from decisions nobody owns. Five 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.
• The sponsor settles scope, not configuration. The sponsor decides whether T&A lives in SAP or elsewhere. The merchandising head decides how it works.
• The solution architect owns the article model. Characteristics, segmentation and seasons touch every module; one person must keep them consistent.
• 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 SAP fashion project cover?

Discovery for an apparel company on SAP 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. SAP partners often run fit-to-standard workshops on a demo system; do that too, but walk the company's own orders first, so the gaps are the business's gaps and not the demo's.

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.

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? Do buyers order in ratio packs or prepacks, or give a size curve?
• What quantity tolerance do buyers allow, and how is a short or over shipment agreed?
• Is one 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?
• How are seasons and collections named, and does each buyer use its own?

Development and sampling

Development questions establish what happens before an article exists.

• Which sample types does each buyer require, and in what order?
• How are sample rounds recorded: sent date, courier, comments, verdict?
• Is there a PLM system today? Which data should it send to SAP, and when?
• 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?
• How are dye lots and rolls labelled, and can the store find every roll of one lot today?
• Which materials are nominated or supplied by the buyer?

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 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, and sold?

Planning and allocation

Planning questions establish channels, segments and who gets scarce stock.

• Which channels share the same stock: wholesale, own retail, e-commerce, outlets?
• Which attributes must keep stock apart: quality grade, country of origin, season, channel? Which of them does the business really act on?
• When stock is short, who decides which order is served first, and on what rule?
• Are operation minutes (SMV) studied per style, taken from a library, or estimated? How is line capacity planned across the season?

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?

Shipping and finance

Shipping and finance questions establish documents, services, currencies and tax.

• How are cartons packed: solid size, assorted, prepack? Which buyers ask for price labels, hangers or special packing?
• Which export documents are prepared per shipment, and who checks them against the letter of credit?
• Which currencies are used for sales, purchases and wages? Which buyers pay by LC, advance or open account, and which deduct chargebacks?
• How is imported material costed today? Is the factory in a free zone or under temporary admission?
• Which e-invoicing and tax reporting rules apply in each country?

7The apparel fit-gap checklist for SAP S/4HANA for fashion: 52 lines

A fit-gap checklist lists every requirement an apparel business has and records, line by line, whether SAP meets it as standard, meets it with configuration, needs an extension, or is better handled outside SAP. The 52 lines below cover product, BOM and costing, materials, production, quality, sales and shipping, and finance.

The answers are our assessment of S/4HANA for fashion and vertical business (on-premise and private cloud) for a typical full-package garment manufacturer. SAP's scope differs by edition and release, and the Public Edition covers less fashion scope than the private edition (section 8). Confirm each line against your release and your partner's demo before you sign a scope.

Key: Standard works as delivered · Configure customising, master data or characteristics · Custom build an extension, a partner add-on or development · Operations layer better run in an apparel operations system and passed to SAP

Counted from this table, 14 of the 52 lines are standard, 24 need configuration, 5 need custom work and 9 are better run outside SAP. That is a better standard score than a general ERP, because the fashion solution was built for articles with variants, seasons and allocation. The operations lines are the same as in every other chapter of this guide: tech packs, measurements, sampling, quoting, line planning, T&A and floor capture. The count is our assessment for a typical full-package manufacturer, not a survey.

8Which SAP edition, and what happens to SAP AFS?

S/4HANA for fashion and vertical business runs on-premise or in SAP's private cloud (SAP S/4HANA Cloud Private Edition), where its full scope is available; SAP S/4HANA Cloud Public Edition has a growing "retail, fashion and vertical business" scope, released in smaller waves. Choose the edition after the fit-gap, and check every fashion feature you need against the scope items of the exact release.

Licensing and prices are negotiated with SAP and depend on the edition, users and scope; we do not quote them. Budget the implementation partner, the SAP competence centre you will need after go-live, and the integrations. From practice, those weigh more than licences in an apparel programme.

When does SAP AFS maintenance end?

SAP's official maintenance statement covers the SAP Business Suite 7 core applications: mainstream maintenance until the end of 2027, and optional extended maintenance until the end of 2030 at an additional two percentage points on the maintenance fee (sources). SAP AFS is an add-on to ECC. Several SAP partners write that AFS maintenance ends in 2027, but they cite no SAP document, and we could not verify whether AFS is covered by the 2030 extended option.

Do not plan an AFS exit on a partner's blog. Check the SAP Product Availability Matrix (PAM) and the SAP Notes for your AFS release, or ask SAP directly, and write the answer and its source into the business case.

Questions to settle before signing

Settle these with SAP and the partner, because each changes the scope, the cost and the upgrade path.

• Which fashion scope items does the fit-gap need, and are all of them in the chosen edition and release?
• Which extensions are planned, where do they run, and who maintains them at each release upgrade?
• Is there a sandbox or quality system for testing each release against real data?
• Which APIs will the integrations use, and are any of them marked deprecated (section 35)?
• For AFS customers: what does SAP confirm in writing about the end of your AFS maintenance?

9SAP S/4HANA for fashion vs SAP Business One for a garment factory

S/4HANA for fashion is a large industry solution with generic articles, seasons, segmentation and allocation as standard; SAP Business One is SAP's ERP for small and mid-size companies, and for apparel it usually relies on a partner add-on for the colour-size matrix. A single-site garment maker is more often weighed between Business One and a mid-market ERP than between Business One and S/4HANA.

Which should a garment company choose?

Choose on scale, channels and the team you can staff. From practice, S/4HANA for fashion pays off when allocation across channels and group-level finance are the main problems; Business One pays off for a single company that wants SAP's accounting with a partner add-on for apparel, and has decided which add-on before any master data is loaded. The SAP Business One chapter covers that path in full, and the comparison page sets both against the other ERPs in this guide.

10How should articles, materials and categories be set up in S/4HANA for apparel?

Set up S/4HANA for apparel by separating the finished garments, which become generic articles with variants, from the materials (fabric, yarn, trims, packaging), which are bought, batched and costed in their own ways; group both in merchandise categories that carry the right characteristics. 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 setup must follow them.

With operations on top: the style, its bill of materials by category and its consumption are built in the operations layer. SAP still needs materials, units and valuation, because it holds stock value and the payables.

11How does S/4HANA for fashion handle style, colour and size?

S/4HANA for fashion models a style as a generic article and each colour-size combination as a variant, created from variant-creating characteristics such as colour, size and fit. This is the SAP Retail article architecture, documented under "Generic Article and Variants" on help.sap.com, and it replaces the AFS grid.

A generic article is the style-level article in SAP Retail and S/4HANA for fashion; its variants are the sellable, stockable articles, one per combination of characteristic values. A variant-creating characteristic is a characteristic whose values produce separate variants; other characteristics only describe the article.

Three further tools shape how the variants are used:

• Application variants restrict which variants may be used on a document such as a sales order, purchase order or stock transfer order. A generic article can hold XS to XXXL while one buyer's orders may use only S to XXL.
• Distribution curves hold quantity ratios across the variant-creating characteristics of a generic article, and can be determined in sales documents. They split a total quantity into sizes by a curve.
• Prepacks are an article category: a set of variants of one or more generic articles bought together and sold individually. SAP's learning content says the prepack components must belong to the same merchandise category as the prepack.

Naming and codes

Agree a numbering rule for generic articles and variants before the first load, for example P2041 for the generic and P2041-NVY-L for a variant, and hold the buyer's own style number separately. Keep one size characteristic per size scale, so an "S" on a polo and an "S" on a bra band never share a value by accident. Govern characteristic values centrally: inconsistent size scales across categories are one of the most common problems SAP fashion consultants report.

With operations on top: styles, colourways and size breakdowns live in the operations layer; SAP needs the generic articles and variants that are actually bought, stocked, sold and invoiced.

12What is segmentation in S/4HANA for fashion, and how should seasons be set up?

Segmentation splits demand and supply of the same article by logical or physical attributes, such as quality, country of origin, season or channel, without creating extra articles. SAP's learning content describes three parts: requirement segments on the demand side, stock segments on the supply side, and a segmentation strategy that says which stock segments may cover which requirement segments in availability check, MRP and supply assignment.

A requirement segment is the segment value on a demand, such as a sales order line for grade A stock; a stock segment is the segment value on stock, such as a batch of grade A goods. A segmentation strategy is the rule that maps stock segments to requirement segments, including where one segment may substitute for another.

Start with the fewest dimensions the business really acts on. Every added dimension multiplies the combinations that planning, availability and allocation must handle, and SAP consultants list too many segmentation dimensions among the main pitfalls. Typical dimensions include quality, country of origin, season and channel; confirm the exact dimensions and their limits in your release.

In SAP S/4HANA Cloud Public Edition, segmentation arrived only in release 2608, as the first wave of demand and inventory segmentation (scope item 82X). A Public Edition project must check what that first wave covers before it designs around segmentation.

How should seasons be set up?

In S/4HANA for fashion, seasons carry purchasing, sales and stock-transfer periods, and the system can determine the season on sales documents, purchase orders and stock transfer orders from those periods. The SAP S/4HANA Cloud 2608 help names the Manage Seasons app (F7465); SAP Fashion Management's documentation describes seasons by year, season, collection and theme, and season determination in production orders.

Keep season, collection and delivery drop separate. From practice, a project that uses the season for everything (buying window, collection, delivery drop, markdown group) ends up with seasons nobody can maintain. Use the season for the time windows SAP uses it for, and hold drops as delivery dates.

With operations on top: the operations layer keeps the order's quality grades and ship clearance; SAP needs segments only where stock value or sales channels require them.

13How do you convert kilograms to metres for fabric in S/4HANA?

SAP converts between units with a fixed factor per article or material as standard, and a fixed kg-to-metre factor is wrong for knit fabric because every roll differs; the SAP answer to a factor that changes per batch is batch-specific units of measure, documented in SAP's logistics help. Knitted fabric is usually bought by weight and cut by length, and the conversion depends on the fabric's weight per square metre (GSM) and its width.

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.

With batch-specific units of measure, SAP's help describes a planned conversion factor held as a characteristic for the material, and an actual conversion factor held on the batch. Until the batch's actual factor is known, the system uses the planned one. SAP's documentation of this feature sits in the SAP ERP logistics help, and a 2025 SAP blog describes it with EWM on S/4HANA 2023 FPS01; it is used mostly in steel, chemicals and pharma. Test it on fashion materials in your release before relying on it, including how it behaves in the fashion BOM and in production order issues.

Three workable designs

There are three workable ways to hold knit fabric in S/4HANA, each with a trade-off.

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 can stay in the purchase unit, kilograms, for stock value and payables.

14How do you track dye lots and fabric rolls in S/4HANA?

Manage fabric in batches and use each batch as one dye lot, with the shade group, measured GSM and width held as batch characteristics through batch classification; then make batch determination at issue respect the dye lot. 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.

SAP's batch management is documented for S/4HANA: batch master records, batch classification with characteristics, and batch determination. SAP fashion consultants add a design rule from practice: fabric without batch management loses its shade and dye-lot history, and turning batches on later is painful. Switch it on for fabric and yarn from day one.

Tracking each roll is a design choice. A batch per roll gives roll-level issue and return but many batches per dye lot, so the dye lot must then be a characteristic. A batch per dye lot with a handling unit per roll keeps the dye lot as the batch and the roll as the package. Pick one and apply it to every fabric.

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. Buyers often allow shade groups within the band (for example A, B and C), and a garment must stay within one group. SAP has no shade band object; the shade group is a batch characteristic, and the judgement against the band happens in inspection.

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 still holds the batch on receipts and issues, so stock value and traceability stay correct.

15How does S/4HANA fashion handle size-dependent fabric consumption in BOMs?

S/4HANA for fashion lets you create one BOM on the generic article whose header and components are copied to the variants, with components that are themselves variants and quantities that can deviate per variant; the consumption numbers still have to come from a marker or a consumption engine. SAP's Fashion Management help describes creating a BOM for a generic article with deviation quantities and include or exclude segment values, copied to the variants (sources).

The detail of how fashion BOMs and routings behave per variant differs between SAP Fashion Management on ECC and S/4HANA for fashion, and the relevant help pages for your S/4HANA release were not all readable when we checked. Confirm the variant BOM and routing behaviour in the fashion manufacturing help for your release, and prove it in the sandbox with a real style before the design is signed.

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. SAP BOMs carry scrap percentages; keep marker efficiency and shrinkage as separate inputs to the consumption calculation, because they come from different people (CAD and lab) and change for different reasons.

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. SAP does not need size-graded BOM quantities to be maintained by hand.

16How do you model cutting, sewing and finishing with SAP work centers and routings?

Model cutting, sewing, finishing and packing as SAP work centers and list the garment's operations with their standard values in a routing; this gives production order operations, capacity requirements and a labour cost, but it does not balance a sewing line. SAP's Fashion Management documentation says manufacturing relies on the standard production scenario with BOMs, task lists and production versions enhanced for fashion.

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. List each one as a routing operation, or group them into a few per department. From practice, grouping keeps confirmations manageable; listing every operation gives a detailed cost but asks the floor for confirmations it will not make.

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 receives material issues and receipts for stock value.

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

S/4HANA for fashion has no object for garment sample rounds, buyer approvals or a T&A calendar, so an SAP project must build them as an extension, take them from a PLM system, or keep them in an operations system. 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. SAP's "PLM system integration for SAP S/4HANA" add-on exchanges data two ways with an external PLM without middleware, which moves released product data into SAP; it does not make SAP the place where sample rounds are run (section 27).

If the project builds sampling inside SAP, the extension needs a sample request per style and colourway with its type, rounds under each request (sent date, courier, pieces, comments, verdict, who recorded it), a link from the approved round to the spec version it approved, a block on the next step (bulk dyeing waits for the lab dip, cutting waits for the PP sample), and T&A milestones that take their actual dates from the rounds.

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 needs none of it.

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

SAP subcontracting uses a purchase order item with the subcontracting item category: the components to provide are listed as sub-items (entered by hand or exploded from the BOM), sent to the supplier, and consumed automatically when the finished item is received. SAP's learning content for S/4HANA purchasing describes this flow, and adds that the goods receipt against the purchase order is mandatory and that component quantities change in proportion when the ordered quantity changes, unless fixed.

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.

Garments often visit several processors: cut panels to a printer, then to a sewing unit, then to a wash. In SAP each step is its own subcontracting purchase order with its own intermediate article, such as "embroidered front, navy, size L". Modelled as one step, the company loses sight of where its goods are between processors.

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 receives the subcontract purchase order and the payable.

19How do you cost a garment in S/4HANA, and where does the garment costing sheet live?

SAP costs articles and production through product costing and production order variances, and adds freight and duty to purchases as planned or unplanned delivery costs; the garment costing sheet used to quote a buyer is built before any generic article exists and usually lives outside SAP. 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.

How do you add freight and duty to imported fabric in S/4HANA?

Enter known import charges as planned delivery costs in the purchase order's conditions, and post charges that only appear on an invoice as unplanned delivery costs at invoice verification. SAP's learning content describes both: planned delivery costs are known when the PO is created and are often billed by a different supplier, such as a forwarder; unplanned ones are entered in logistics invoice verification and are distributed across the invoice items or posted to a separate account, depending on configuration.

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. How a planned delivery cost is split across PO items depends on its condition type (a fixed amount, a quantity-based rate or a percentage of value). For a factory in a free zone or under temporary admission, duty may be zero or suspended; agree the rules 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 holds the delivery costs that actually hit the purchases, for stock value.

20Can SAP QM run AQL inspection for garments?

SAP Quality Management (QM) creates inspection lots, for example on goods receipt, records results per inspection characteristic, and calculates sample sizes from sampling procedures; sampling schemes built on ISO 2859-1 tables are what SAP QM practitioners use for AQL. The buyer's inspection level per order and the garment defect catalogue still need design. 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.

SAP QM concepts a garment project uses: inspection lots (created by an event such as a goods receipt), inspection characteristics (what is checked), sampling procedures (how many pieces), defect records and the usage decision, which accepts or rejects the lot and is recorded with the user who took it. Stock under inspection stays in quality inspection stock until the usage decision. Which sampling schemes your system delivers, and how the AQL value is chosen per lot, differ by setup; confirm both before promising a buyer's plan.

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 sees the delivery once it is cleared.

21How do you handle cartons, VAS and shipping documents in S/4HANA for fashion?

SAP packs deliveries into handling units, which represent cartons and pallets, and S/4HANA for fashion adds value-added services (VAS), such as price labels and special packing, that can be requested per customer and carry their cost. Buyer carton labels and pack-level packing lists are forms to build per buyer.

A handling unit is SAP's record of a physical package, such as a carton, with its contents and its packaging material. VAS (value-added services) in SAP's fashion and retail documentation are services performed on goods before delivery, such as ticketing, hanging or special packing, held as requirements the warehouse follows and whose cost can be recorded.

With operations on top: shipments per delivery, packing and cartonisation, and ship clearance against the buyer's terms run in the operations layer. SAP receives the dispatch and bills the customer.

22What is supply assignment (ARun) in S/4HANA for fashion?

Supply assignment, often called ARun (allocation run), assigns existing and incoming stock to open requirements such as sales orders and stock transfers, and automates their release for delivery. SAP's learning content describes it as the fashion solution's way to decide which demand gets which supply when stock is short. Grouping rules bundle requirements, and supply assignment can run online or in batch, including for variants.

Supply assignment matters most to brands and vertical retailers with several channels competing for the same stock. For a make-to-order factory whose production is tied to one buyer order, it matters less: the stock was made for that order. It works with segmentation, because the segmentation strategy decides which stock segments may be assigned to which requirement segments.

23How does S/4HANA handle multi-currency, letters of credit, down payments and chargebacks?

SAP S/4HANA Finance handles foreign currencies, exchange differences, period-end valuation of open items and down payments as standard; chargebacks are handled with reason codes on payment differences; a letter-of-credit object depends on which SAP trade components the company licenses. 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 payments

In SAP sales, a down payment is requested with a down-payment request, commonly driven by a billing plan on the sales order, and the payment received is cleared against the final invoice. Confirm the billing plan and document types your partner configures, and test the tax treatment of the down payment in your country.

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. Whether your SAP licence includes a letter-of-credit record with expiry and latest-shipment-date checks depends on the components you run; confirm it with SAP before designing a custom one.

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. In SAP receivables, the shortfall is posted as a payment difference with a reason code, so every deduction is classified at the moment the cash is applied. Without reason codes, nobody can tell whether the company loses money to labels or to lateness.

With operations on top: finance stays in SAP 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.

24Does S/4HANA support e-invoicing and localisation for garment exporting countries?

SAP delivers country versions for S/4HANA and handles electronic invoices and statutory reports through SAP Document and Reporting Compliance, which generates electronic documents such as invoices, waybills and credit notes and submits them to authorities; which countries and which documents are covered depends on the release, so check SAP's "supported compliance tasks by country/region" list for yours.

We have not verified SAP's coverage for Egypt, Pakistan, Bangladesh, India, Vietnam, Morocco, Tunisia or Turkey in this guide. Check the country list for your release, ask the partner which statutory reports it has delivered in that country before, and test an e-invoice end to end in the quality system before go-live.

Factories in free zones or under temporary admission often report the import and re-export of materials to customs. SAP's material documents carry the quantities; the report format is local and usually an extension or a partner solution.

25In what order should you configure S/4HANA for an apparel company?

Configure S/4HANA for apparel from the organisation outward: enterprise structure, finance and currencies first, then the article model (characteristics, merchandise categories, seasons, segmentation), then units and batches, then purchasing, sales and production, then quality, packing and allocation, and only then the master data. Each step depends on the one before it; loading generic articles before the characteristics and segmentation are final means reloading them.

We give no menu paths or transaction codes here: they differ between SAP GUI, Fiori apps and editions, and SAP's help is the reference. The sequence below is from implementation practice.

26How should an apparel project extend S/4HANA without breaking upgrades?

Extend S/4HANA for apparel with the least invasive option that works: key-user extensions for fields and simple logic, developer extensions on released APIs where the logic must sit close to SAP, and side-by-side applications on SAP BTP for whole functions such as sampling or T&A. SAP's guidance calls this keeping a clean core, and it names the three types: key user (on-stack), developer (on-stack) and side-by-side on SAP Business Technology Platform.

From practice: modifications to SAP's own code are what make a release upgrade expensive, and an apparel project that pushes sampling, T&A and floor capture into the core accumulates exactly those. The Public Edition allows fewer extension types than the private edition; check the rules for your edition before designing.

Every extension needs an owner, a reason and a test that runs at each upgrade. Keep a register, and move anything that is really a whole process (sampling, T&A, planning, floor capture) out of the core into a side-by-side application or an operations system.

27Which systems does an SAP fashion implementation integrate with, including PLM?

An S/4HANA fashion implementation typically connects to a PLM or tech-pack system, an operations layer or shop-floor system, EDI with retailers, banks and tax authorities; each connection needs one owner per field and links stored on SAP's permanent document and master-data keys. SAP offers an add-on, "PLM system integration for SAP S/4HANA", that exchanges data two ways with external PLM systems without middleware.

Centric Software states that its PLM pushes and pulls data to SAP and has offered a REST API since 2017. We found no certified Centric connector for S/4HANA; check with both vendors and do not assume one exists. For EDI and other connections, SAP Integration Suite or the company's existing middleware is the usual route; confirm the options in SAP's documentation for your landscape.

Rules for every connection

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

• Link on SAP's keys, the document number or master-data key SAP assigns, never on a description or a code a user can 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. Compare quantities and prices from the other system; never overwrite silently.
• Make receivers safe to call twice, so a retried message does not create a second purchase order.

28How do you migrate apparel data into S/4HANA, and from SAP AFS?

Migrate only open and active apparel data (active styles as generic articles, open orders, open purchase orders and stock by batch) with the SAP S/4HANA Migration Cockpit, in dependency order, and have each department head sign off the loaded figures; AFS customers also have SAP's Data Transport and Migration Tool (DTMT) for Fashion. History stays in the old system or an archive.

The Migration Cockpit is SAP's standard tool for loading data into S/4HANA. SAP's documentation describes the "Migrate Your Data" app, migration objects that define what is loaded, and two approaches: direct transfer from certain SAP source systems, and staging tables filled from template files or tools such as SAP Data Services. SAP's learning content for S/4HANA for fashion covers the Migration Cockpit, including AFS sources. DTMT for Fashion is an ETL tool for moving business-object data between ABAP-based SAP systems; SAP's AFS-to-fashion migration guide describes it converting a material with an AFS grid into an article, and it can also move custom tables.

Load order

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

AFS migration pitfalls

AFS migrations fail in recognisable ways. The list below combines SAP's migration guidance with implementation practice.

• Lifting the AFS grid one to one. Redesign the generic-article and characteristic model first; convert second.
• Carrying AFS categories into too many segmentation dimensions. Map only the dimensions the business still acts on.
• Inconsistent size scales across categories. Clean and govern characteristic values before the load, one scale at a time.
• Fabric migrated without batches. Shade and dye-lot history is lost for good; load stock by batch with its characteristics.
• Custom AFS code ported blindly. List every custom program, keep only what the new standard does not cover, and move processes out of the core where possible (section 26).
• Integrations built on deprecated APIs. Check each API's status on api.sap.com before migrating an interface (section 35).

The cut-off rule and cleansing

A cut-off rule states the exact moment after which every transaction is entered in S/4HANA and not in the old system. Write it as a date and time, name what happens to documents in flight, and count stock at the cut-off. Clean data before it is loaded, never after: merge duplicate suppliers and materials, retire styles with no order in two seasons, give every fabric one base unit and every roll its batch, and split partly delivered order lines into delivered and open quantities.

Generic article,Variant,Colour,Size,Merchandise category,Season
P2041,P2041-NVY-S,NAVY,S,MEN-POLO,AW26
P2041,P2041-NVY-M,NAVY,M,MEN-POLO,AW26
P2041,P2041-NVY-L,NAVY,L,MEN-POLO,AW26
P2041,P2041-NVY-XL,NAVY,XL,MEN-POLO,AW26
P2041,P2041-NVY-XXL,NAVY,XXL,MEN-POLO,AW26

Legacy order,Item,Article,Quantity,Unit price,Net value
SO-P2041,10,P2041-NVY-S,300,4.26,1278.00
SO-P2041,20,P2041-NVY-M,750,4.26,3195.00
SO-P2041,30,P2041-NVY-L,900,4.26,3834.00
SO-P2041,40,P2041-NVY-XL,750,4.26,3195.00
SO-P2041,50,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, plant stock, not batch-managed

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.

29How should you test an SAP S/4HANA fashion implementation end to end?

Test an S/4HANA fashion implementation with end-to-end scenarios that follow one real order from the buyer's PO to cash, run by the business's key users on migrated data in the quality system, each step with an expected result written down before the test starts. Unit tests of each configuration prove the settings work; 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.

Test script: subcontract embroidery with loss

Scenario T5 proves that components provided, fronts received and fronts lost add up (Example 18).

Test script: short shipment within tolerance

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

30How should you train an apparel company's staff on S/4HANA?

Train each role only on the Fiori apps and scenarios it will use, in the local language, on the company's own styles and orders, and have key users teach their colleagues. A merchandiser does not need the finance apps, and a floor supervisor needs one screen that works, not an introduction to SAP.

Hours are practice, not a standard; adjust them to the team and the scope. Floor operators are trained on whatever captures floor output. If that is a kiosk or scanner screen, the training is minutes; if it is SAP confirmation apps on the floor, expect the data never to arrive.

31What does an S/4HANA cut-over plan look like for an apparel company?

An S/4HANA cut-over plan is a day-by-day list of the steps that move the company from the old system to S/4HANA: freeze, final loads with the Migration Cockpit, 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 in full at least once, in a system that is a copy of production.

The fall-back decision belongs at the noon go or no-go: if the counted stock and the open orders do not reconcile, the company keeps working in the old system rather than going live on figures nobody trusts.

32When should an apparel company go live on S/4HANA, and how long is hypercare?

Go live between seasons, in the lowest-volume weeks and away from peak shipment windows, and keep the partner in close support until at least the first month-end close in S/4HANA is complete. 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. For a brand, also avoid the start of a selling season, when allocation runs daily.
• Duration. Practitioners commonly plan hypercare of four to eight weeks for an ERP go-live, and longer for a multi-country SAP rollout. That is judgement, not a measured standard; the rule that matters is that nobody leaves before the first month-end close is complete.
• Issue log. One list: date, who, what happened, severity, owner, status. Review it daily in the first two weeks.
• Exit criteria. The month-end closes on time, no issue blocks shipping or billing, and key users handle first-line questions.

33What are the most common mistakes when implementing S/4HANA for fashion?

The most common mistakes in S/4HANA fashion projects are lifting the AFS grid one to one, too many segmentation dimensions, ungoverned size scales, fabric without batches, one season for everything, integrations on deprecated APIs, and pushing sampling and floor processes into the core. The list below comes from SAP fashion consultants' experience and general implementation practice, not from SAP's documentation.

1. The AFS grid lifted one to one.The generic article and characteristic model is different; a straight copy repeats every old problem.
2. Too many segmentation dimensions.Each one multiplies the combinations planning must handle. Start with one or two.
3. Size scales not governed.The same "M" means different things in different categories, and reports stop adding up.
4. Fabric without batch management.Shade and dye-lot history is lost; switching batches on later is painful.
5. One conversion factor for all fabrics.Stock value looks right while the cutting room runs short.
6. Seasons used for everything.Season, collection and delivery drop get tangled; keep them separate.
7. The generic BOM holds the base size only.Large sizes run short (Example 14).
8. Deprecated APIs.An interface is built on a V2 service already marked deprecated, such as the old purchase-order process API.
9. Edition chosen before the fit-gap.A Public Edition project discovers that a fashion scope item it needs is not in its release.
10. Sampling, T&A and floor capture pushed into the core.Every release upgrade gets harder.
11. AFS end-of-maintenance date taken from a blog.The business case rests on a date nobody confirmed with SAP.

The 15 general failure modes, and how each shows up in S/4HANA

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

34What must be decided before an S/4HANA fashion go-live?

Decide the generic-article level, the variant-creating characteristics, the segmentation dimensions and strategy, the season model, the unit and batch design for every fabric, the edition and its scope items, 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:

• Generic article at style or style-colour level; the numbering rule for variants.
• Variant-creating characteristics and governed values per size scale.
• Application variants per document type and customer.
• Segmentation dimensions (start minimal) and the segmentation strategy.
• Season model: seasons, collections, periods; delivery drops kept separate.
• Distribution curves and the rounding rule.
• Unit design for every fabric and yarn; batch-specific units tested or not used.
• Batch per dye lot or per roll; mandatory batch characteristics at receipt.
• How size-graded consumption reaches the BOM.
• Delivery-cost conditions and how each is split.
• Sampling procedures per buyer plan, and who may take a usage decision.
• How buyer-supplied fabric is held so it never enters stock value.
• Supply assignment rules and who owns them.
• Edition, release and the scope items the fit-gap needs, checked line by line.
• The extension register: what is key user, developer or side-by-side.
• Which system owns sampling, T&A, planning, floor capture and quality.
• Every integration on a non-deprecated API, with its communication arrangement.

35Which SAP S/4HANA APIs should an apparel integration use?

Build S/4HANA integrations on the OData APIs published on the SAP Business Accelerator Hub (api.sap.com), prefer the OData V4 services where SAP has deprecated the V2 ones, and expose each through a communication arrangement with its own communication user. SAP releases and deprecates APIs per release, so check each API's status on api.sap.com for yours before building.

• Authentication. APIs are exposed through a communication arrangement for a communication scenario (SAP's documentation names, for example, SAP_COM_0102 for purchase requisition integration), with a communication user. SAP's documentation for the purchase order APIs mentions basic authentication and OAuth 2.0; your Basis team decides which is allowed.
• Identifiers. Link on SAP's document keys, such as the purchase order number and item, and the article number. In SAP, a document number is assigned when the document is created and is not edited afterwards, so the PO number serves as the permanent id.
• Fashion fields. Whether the APIs carry segmentation values, seasons and generic-article references in your release is not something we could verify. Check the entity sets and $metadata before designing the field map.
• Limits. Throughput, batch sizes and concurrent calls depend on the landscape; agree them with the Basis team rather than assuming.
• Push and pull. Polling on a changed-on date or a status is the dependable baseline. If you use SAP event-based integration or middleware to push changes, make the receiving side safe to call twice.
• No silent overwrites. Compare quantities and prices coming from SAP with the operations layer's values and show differences to a person.

POST /api/v1/erp/po-status
Idempotency-Key: sap-po-4500012457-created

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

The no-code option. Where no integration team is available, the same exchange runs as a file: MerchandiserOS exports the purchase requests, the SAP team loads them, and a file of "request, SAP PO number, status, date" comes back into MerchandiserOS, where a person approves each row before it is recorded. The ERP API guide documents both routes.

36If you don't manufacture: brands, buying agents and own-label retailers on S/4HANA

A brand, a buying house or an own-label retailer uses S/4HANA for fashion for the buying, selling and money side: purchase orders to factories, landed cost and duty, vendor payments, wholesale and retail sales, supply assignment across channels, EDI with retailers and multi-currency. It should skip the manufacturing scope. What SAP handles poorly for these businesses is the work that happens at other people's factories: development and sampling, T&A, following production, inspections at the vendor, and one status per order across many factories.

Who they are

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

S/4HANA for fashion was built largely for the first and third: SAP's own introduction describes retail, wholesale and manufacturing "under one roof", and its allocation features serve brands and vertical retailers first. As an ERP for fashion brands it is strong. As a buying house ERP it is usually far larger than the business, because an agent holds no stock and invoices one thing, its commission.

What they need from S/4HANA, and what to skip

The table lists what a brand, agent or own-label retailer needs and the S/4HANA feature that answers it.

Skip the manufacturing scope. A brand that does not own factories does not need work centers, routings, production orders, fashion BOM explosion into production or shop-floor confirmations. Drop them from the fit-gap, the configuration and the training. The one exception is a brand that buys fabric and sends it to a CMT factory: that is a subcontracting purchase order, not production.

What S/4HANA handles poorly for them

The work that makes or breaks a brand's season happens outside its own walls, and SAP has no natural home for most of it.

• Development and sampling with many factories. Lab dips, strike-offs, fit and PP samples arrive from several vendors, round by round. SAP has no sample-round object (section 17).
• T&A across factories. Each order's milestones sit at a different vendor, and the critical path crosses them.
• Following production that happens outside. The brand's purchase order is open in SAP, but cutting, sewing and packing are at the factory; SAP sees only the goods receipt.
• Inspections at the vendor. AQL inspections happen at the factory before shipment, often by the brand's own QA staff or an agent. SAP QM inspection lots are built around the brand's own receipts.
• One status per order across many factories and buyers. A merchandiser needs one line per order showing where it is; SAP shows documents, not the order's story.

The MerchandiserOS model for brands and agents

For a business that does not manufacture, MerchandiserOS runs development, samples and approvals, T&A, the orders placed with factories, sourcing, the planning view across subcontracted factories, quality inspections and shipping follow-up. S/4HANA keeps the books: payables to factories, landed cost and stock value, receivables, payments, tax and e-invoicing, and for a brand also its sales and allocation. MerchandiserOS offers "Brand" and "Buying agent" workspace set-ups for these businesses. Retail back-office work, such as stores, point of sale, allocation and open-to-buy, is outside MerchandiserOS's scope; for a brand on S/4HANA for fashion, that stays in SAP.

·Glossary of apparel and SAP terms

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

AFS

SAP Apparel and Footwear: an add-on to R/3 and ECC that held styles as materials with a colour-size grid; replaced by S/4HANA for fashion.

Application variant

In S/4HANA for fashion, a restriction on which variants of a generic article may be used on a document such as a sales order or purchase order.

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.

ARun

Supply assignment: the fashion solution's run that assigns existing and incoming stock to open requirements and releases them for delivery.

Batch

In SAP, a quantity of a material with the same properties, tracked separately; for fabric, one dye lot.

Batch classification

Characteristics held on a batch, such as shade group, GSM and width.

Batch-specific unit of measure

An SAP feature where the conversion between two units is held per batch instead of as one fixed factor.

BOM

Bill of materials: the list of components and quantities to make one product.

CM, CMT

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

Communication arrangement

In S/4HANA, the setting that exposes a set of APIs (a communication scenario) to a named external system and user.

Distribution curve

In S/4HANA for fashion, quantity ratios across a generic article's variants, used to split a total into sizes.

DTMT for Fashion

SAP's Data Transport and Migration Tool, used to migrate data from AFS to SAP's fashion solutions.

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.

Delivery costs

In SAP purchasing, freight, duty and similar charges, planned on the purchase order or unplanned at invoice verification.

FOB

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

Generic article

The style-level article in SAP Retail and S/4HANA for fashion; its variants are the stockable colour-size articles.

GSM

Grams per square metre: the weight of fabric.

Handling unit

SAP's record of a physical package, such as a carton, with its contents.

Landed cost

Every cost of bringing goods in 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.

Migration Cockpit

SAP's standard tool for loading data into S/4HANA, by direct transfer or staging tables.

OData

The web API protocol behind most S/4HANA APIs; SAP publishes V2 and V4 services.

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.

Prepack

An SAP article category holding variants of one or more generic articles, bought together and sold individually.

Requirement segment, stock segment

The segment values on a demand and on stock; a segmentation strategy maps one to the other.

Season

In S/4HANA for fashion, a time frame with purchasing, sales and stock-transfer periods, determined automatically on documents.

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.

Style/colour/size matrix

A grid of colours by sizes used to enter or show order quantities for each combination.

T&A calendar

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

Usage decision

In SAP QM, the recorded decision that accepts or rejects an inspection lot.

VAS

Value-added services: work such as ticketing or special packing done on goods before delivery, held as requirements with their cost.

Variant-creating characteristic

A characteristic, such as colour or size, whose values create separate variants of a generic article.

·Checklists: an S/4HANA fashion implementation on one page

The checklists below repeat the decisions and checks from each part of this guide, in project order.

Discovery

Discovery is complete when every item below is ticked.

• Business type settled for each part of the business: brand, own-label retailer, full package, CMT, agent.
• One decision owner named for each area, and a solution architect for the article model.
• One workshop per department, walking a real recent order.
• All 52 fit-gap lines answered with evidence, decision and owner.
• Architecture decided: what SAP owns, what runs in an operations layer.
• Edition and release chosen after checking every fashion scope item the fit-gap needs.
• For AFS customers: the end-of-maintenance date confirmed with SAP in writing.

Design

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

• Generic-article level, variant-creating characteristics, governed size scales.
• Application variants, distribution curves and the rounding rule.
• Segmentation dimensions (minimal) and strategy; season model with drops kept separate.
• Unit design per fabric; batch per dye lot or per roll; batch characteristics.
• Consumption source for size-graded BOM quantities.
• Work centers, routings and minutes; what stays in planning outside SAP.
• Subcontract steps, one purchase order per processor.
• Delivery-cost conditions and their split.
• Inspection types, sampling procedures, usage-decision rights.
• Handling units, VAS, carton labels and buyer documents.
• Currencies, down payments, LC handling, chargeback reason codes, e-invoicing.

Build, data and testing

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

• Configuration done in dependency order, on the go-live release.
• Extensions registered by type (key user, developer, side-by-side) with owners.
• Integrations on non-deprecated APIs, linked on SAP keys, one writer per field.
• Migration loaded with the Migration Cockpit or DTMT, 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 company's own orders.
• Cut-over rehearsed once in full.
• Go-live date between seasons, away from year-end, audits and selling peaks.
• Go or no-go point and fall-back defined.
• Hypercare runs at least until the first month-end close in S/4HANA.

Other chapters of this guide cover the ERPs most often weighed against SAP: SAP Business One, Dynamics 365 Finance and Supply Chain Management and Infor. The methodology and the full glossary apply to all of them.

·Sources

SAP pages were checked on 26 September 2026. Several help.sap.com pages render only with JavaScript; where we relied on a page's title or search summary rather than its full text, the claim in the guide is worded cautiously and tells you to check your release.

1. SAP, SAP S/4HANA for fashion and vertical business, product page — sap.com · help.sap.com product documentation — help.sap.com
2. SAP Community, SAP S/4HANA for fashion and vertical business: retail, wholesale and manufacturing under one roof — community.sap.com
3. Rizing, Introduction to SAP S/4HANA for fashion and vertical business — rizing.com
4. SAP Community, SAP S/4HANA Cloud Private Edition and SAP S/4HANA for fashion, 2022 release — community.sap.com
5. SAP Community, What's new in retail, fashion and vertical business for SAP S/4HANA Cloud 2608 (scope item 82X) — community.sap.com
6. SAP News, SAP mainstream maintenance commitments (2020) — news.sap.com · SAP Support, maintenance strategy for S/4HANA and Business Suite 7 — support.sap.com
7. Partner statements on AFS ending in 2027 (not SAP sources) — xeptum.com · rizing.com
8. SAP Apparel and Footwear 6.4, master guide — help.sap.com · SAP Fashion Management documentation — help.sap.com
9. SAP Help, Generic Article and Variants (S/4HANA) — help.sap.com · SAP Community, smooth migration from AFS to S/4HANA for fashion, part I — blogs.sap.com
10. SAP Help, application variants (SAP Fashion Management) — help.sap.com
11. SAP Help, distribution curves — help.sap.com · help.sap.com
12. SAP Learning, Structured articles (prepacks) — learning.sap.com
13. SAP Learning, Explaining segmentation — learning.sap.com
14. SAP Help, Determination of Seasons (SAP S/4HANA Cloud 2608, Manage Seasons app F7465) — help.sap.com · Determination of seasons in sales documents — help.sap.com · Season (SAP Fashion Management) — help.sap.com
15. SAP Help, value-added services — help.sap.com · help.sap.com
16. SAP Learning, Explaining supply assignment — learning.sap.com · SAP Help, supply assignment for variants (SAP Fashion Management) — help.sap.com
17. SAP Help, Creating a BOM for a generic article (SAP Fashion Management) — help.sap.com · Production version — help.sap.com
18. SAP Help, Batch management and batch classification (S/4HANA) — help.sap.com · help.sap.com
19. SAP Help, Batch-specific units of measure in logistics (SAP ERP) — help.sap.com · SAP Community, batch-specific unit of measure with EWM on S/4HANA 2023 FPS01 — community.sap.com
20. SAP Learning, Working with subcontracting (S/4HANA purchasing) — learning.sap.com
21. SAP Learning, Entering delivery costs — learning.sap.com · SAP Help, Unplanned delivery costs — help.sap.com
22. SAP Community Q&A, sampling schemes and AQL selection in SAP QM (practitioner source) — community.sap.com
23. SAP Help, Document and Reporting Compliance — help.sap.com · Supported compliance tasks by country/region — help.sap.com
24. SAP Community, Extensibility options for the clean core journey — community.sap.com
25. SAP Help, PLM system integration for SAP S/4HANA — help.sap.com · Centric Software, What is Centric PLM (vendor claim) — centricsoftware.com
26. SAP Learning, Migrating with the Migration Cockpit (S/4HANA for fashion) — learning.sap.com · SAP Help, Migrate Your Data – Migration Cockpit — help.sap.com
27. SAP, DTMT for Fashion migration guide (AFS2FMS) — help.sap.com · Administrator's guide — help.sap.com
28. SAP KBA 3396486 (API_SALES_ORDER_SRV) — support.sap.com
29. SAP KBAs on the purchase order API: 3502308 — support.sap.com · 3365110 — support.sap.com · 3555741 — support.sap.com · SAP Help, OData V4 API: Purchase Order — help.sap.com
30. SAP Help, OData V4 API: Purchase Requisition — help.sap.com · SAP Community, What's new in purchase requisitions, Public Edition 2508 — community.sap.com · SAP Community, Purchase requisition OData API (SAP_COM_0102) — blogs.sap.com
31. SAP Business Accelerator Hub, Material Documents – Read, Create (API_MATERIAL_DOCUMENT_SRV) — api.sap.com
32. SAP Help, OData API: Production Order (Version 2) — help.sap.com · SAP KBA 3703125 — support.sap.com
33. SAP Business One, item variants and the matrix (partner sources) — sana-commerce.com · emerging-alliance.com · Service Layer v1 and v2 — help.sap.com
34. ISO 2859-1, Sampling procedures for inspection by attributes — iso.org · AQL tables and acceptance numbers — qima.com
35. UCP 600, documentary credits — tradefinanceglobal.com

Corrections. SAP changes between releases and editions, and a scope item, an API status 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 release 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 facts in this chapter at least once a year and after each major S/4HANA release.

SAP, SAP S/4HANA, SAP Business One, SAP Fiori and other SAP product names are trademarks or registered trademarks of SAP SE, used here only to name the products. This guide is not endorsed by SAP SE. Centric Software is a trademark of its owner. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.