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

1Who NetSuite fits

Oracle NetSuite fits apparel brands, wholesalers and multi-company groups best, and fits garment manufacturers when the factory accepts that cutting, sewing and floor control need extra SuiteApps, partner products or a separate operations system. It is a cloud ERP sold as a subscription, with strong order-to-cash, procure-to-pay, multi-location stock and multi-subsidiary accounting through OneWorld.

For apparel, NetSuite's natural model is the matrix item: a parent item for the style and a child item for each option combination, such as navy in size L. Oracle adds a Grid Order Management SuiteApp for grid entry on orders, and a SuiteSuccess edition for Apparel, Footwear and Accessories that preconfigures an account for the industry. Manufacturing depth comes from assembly items, work orders, Advanced Bill of Materials, Manufacturing WIP and Routing, the Advanced Manufacturing SuiteApp and Outsourced Manufacturing.

Signs NetSuite is a good choice

NetSuite tends to work when the business values one cloud ledger across companies and channels more than deep factory control.

• The group has several legal entities, currencies or countries, for example a brand in Europe with a sourcing office and a factory in another country. OneWorld is built for that.
• A large share of revenue is wholesale, e-commerce or retail, where NetSuite's order management, commerce connectors and multi-location stock carry weight.
• The factory accepts a SaaS model: no server of its own, upgrades on Oracle's release calendar, and customisation through SuiteCloud rather than changes to core code.
• An implementation partner with manufacturing and apparel experience is available, or the factory will run production in a separate system and keep NetSuite for finance, purchasing and stock.

Signs to slow down

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

• The factory expects NetSuite to plan sewing lines, balance operations and track bundles. Work orders and routings do not do that (section 16).
• The style range is wide enough that one style's colour, size and length combinations approach 2,000 (section 11).
• Knit fabric is bought by weight and cut by length, and nobody has decided how kilograms become metres per roll (section 12).
• An existing integration uses SOAP or token-based authentication and nobody has planned the move before the 2027.1 and 2028.2 deadlines (section 34).
• 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. This is not a NetSuite weakness. NetSuite even ships an apparel edition and a grid SuiteApp, and the matrix still arrives after the costing, the lab dips and the fit samples are done. SAP, Dynamics 365, Odoo and every general ERP meet the same wall. Brands, buying agents and own-label retailers meet it too: their development, sampling and follow-up across factories happen before and around the transactions the ERP records (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. In NetSuite that customisation is SuiteScript and custom records, which run under governance limits and must be retested at every twice-yearly release. 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 36 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: NetSuite keeps the books, and an operations system built for apparel runs everything from the style to the shipment.

With this split, the NetSuite project stays close to standard: fewer SuiteScripts, fewer custom records, a smaller call on the account's API concurrency and a cleaner path through each release. The rest of this guide still explains how to bend NetSuite toward garment production, because some factories choose to, and because a consultant needs to know what each choice costs. Where an area moves out of NetSuite under the recommended model, the section ends with a short note. Section 35 describes the model in full, department by department.

4Business types, and what each needs from NetSuite

"Apparel business" covers very different companies, and the business type decides which parts of NetSuite carry weight. Settle it in the first discovery meeting, because one group often runs two types at once, for example a brand subsidiary that buys finished goods and a factory subsidiary that sews them.

The list above is general implementation practice. Treat it as a starting point for the discovery questions in section 6, not as a scope. Brands, buying agents and own-label retailers that make nothing themselves have their own Part in this guide (section 35). A group that runs a brand and a factory as separate subsidiaries in OneWorld can give each subsidiary its own flows while sharing items and suppliers; decide that structure early, because the subsidiary hierarchy and each subsidiary's base currency are hard to change later (section 8).

5Who should be on a NetSuite apparel project team?

A NetSuite apparel project needs one decision owner for every design question, and most of those owners sit in the business, not in IT. The partner configures, scripts and integrates; the factory or brand decides how styles, units, lots, 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 company. 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. 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 NetSuite or elsewhere. The merchandising head decides how it works.
• Name an in-house administrator from day one. NetSuite is SaaS, so the release calendar is Oracle's. Someone inside the business must own sandbox testing of each release after the partner leaves.
• 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 a NetSuite apparel project cover?

Discovery for an apparel NetSuite project 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 business's own orders, not a demo account. 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 business's own, and add the NetSuite-specific questions at the end of each list.

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?
• 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?
• NetSuite: how many colours, sizes and lengths does the widest style carry, and how many new colours arrive mid-season? This sizes the matrix against the 2,000 ceiling.

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, lots 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 or supplied by the buyer?
• NetSuite: will bins be used (Advanced Bin / Numbered Inventory Management), and is a roll a lot, a bin or a custom record?

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?
• NetSuite: should materials sit in a WIP account between issue and completion (Manufacturing WIP), or is a one-step assembly build enough?

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 by EDI?

Finance

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

• How many legal entities are there, in which countries and base currencies? Which trade with each other?
• Which currencies are used for sales, purchases and wages? How are exchange differences booked today?
• How are buyers paid: letter of credit, advance, open account? Which buyers deduct chargebacks?
• How is imported material costed: are freight, duty and clearing added to the material cost, and by weight, quantity or value?
• Which costing method does each class of item need: standard for finished garments, average or lot costing for fabric?
• Is the factory in a free zone or under a temporary-admission regime, and what reports does that require? Which e-invoicing rules apply?

7The apparel fit-gap checklist for NetSuite: 52 lines

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

The answers are our assessment of NetSuite, as documented in Oracle's online help in September 2026, for a typical full-package garment factory. "Configure" includes Oracle SuiteApps such as Grid Order Management, Advanced Manufacturing and Quality Management, which are separate installs and in some cases separately licensed; check each with Oracle or your partner. Confirm every line against your account before you sign a scope.

Key: Standard works with NetSuite features switched on · Configure settings, custom fields, saved searches or an Oracle SuiteApp · Custom build SuiteScript, custom records or a partner product · Operations layer better run in an apparel operations system and passed to NetSuite

Counted from this table, 6 of the 52 lines are standard, 26 need configuration or an Oracle SuiteApp, 11 need custom build and 9 are better run outside NetSuite. That count is our assessment for a typical full-package factory, not a survey. A brand buying finished goods drops most of the production lines and scores far better; a CMT factory drops most of the costing and material lines; a mill adds process lines this list does not cover.

8NetSuite editions, SuiteApps, OneWorld and service tiers for apparel

A NetSuite apparel project chooses four things beyond the base licence: whether to start from the SuiteSuccess Apparel, Footwear and Accessories edition, whether OneWorld is needed for several subsidiaries, which Oracle SuiteApps the fit-gap calls for, and which service tier the account runs on, because the tier sets the API concurrency every integration shares. Oracle does not publish NetSuite list prices, so every cost line below is a question for Oracle or the partner.

What is the NetSuite Apparel, Footwear and Accessories edition?

The Apparel, Footwear and Accessories (AFA) edition is one of NetSuite's SuiteSuccess editions: a NetSuite account configured for the industry, with predefined roles, dashboards, KPI scorecards, reports, saved searches, forms and preferences, and business processes delivered through SuiteApps. Oracle's help lists it as one of eight SuiteSuccess industries. It is a starting configuration of NetSuite, not a separate product, and it is often called SuiteSuccess Apparel. It is not the same thing as SAP's older AFS add-on, which is an unrelated SAP product.

We could not read Oracle's AFA brochure (the file refused access when checked), so we do not list what the edition contains beyond Oracle's general SuiteSuccess description. Ask Oracle for the current AFA scope in writing and map it against the 52 lines in section 7. In our experience the gaps in the operations-layer column remain open in any edition, because they are about the product before the item exists.

Which SuiteApps and features does an apparel project usually switch on?

A garment manufacturer running production in NetSuite usually needs the items, assembly and work-order features plus several Oracle SuiteApps; a brand needs fewer.

Oracle notes that the Advanced Manufacturing SuiteApp's post-implementation setup is configured together with NetSuite Professional Services. Plan for that in the timeline.

When does an apparel business need NetSuite OneWorld?

An apparel business needs OneWorld when it runs more than one legal entity in NetSuite, for example a brand company and a factory company, or factories in two countries. Each subsidiary has its own base currency, and Oracle's help is explicit that a subsidiary's base currency cannot be changed after the subsidiary record is first saved. Treat the subsidiary structure and base currencies as the first decision of the project, not a setting to tidy up later.

What does the service tier have to do with an apparel project?

The service tier sets how many web-service and RESTlet requests the account accepts at the same time, and every integration shares that number. A factory that connects e-commerce, EDI, a floor system and an operations layer can run out of concurrency before it runs out of anything else. Oracle's published base limits are 5 for Standard, 15 for Premium, 20 for Enterprise and 20 for Ultimate on the current tiers, and each SuiteCloud Plus licence adds 10. Section 34 works through a budget.

How much does NetSuite cost for a garment business?

The cost depends on the base licence, the modules and SuiteApps licensed, the number of full users, the service tier, any SuiteCloud Plus licences and the partner work; Oracle quotes NetSuite privately and does not publish a price list, so we give no figures. Put these lines in the comparison:

Questions to settle with Oracle and the partner

Settle these before signing, because each changes the cost and the path through future releases.

• Which SuiteApps does the fit-gap need, which are licensed separately, and which need Professional Services?
• What does the AFA edition contain today, in writing, line by line against the fit-gap?
• Which service tier, how many sandboxes, and how much API concurrency is left once every planned integration is counted?
• Which scripts and custom records are planned, who owns their code, and who retests them at each release?
• Is any existing integration on SOAP or token-based authentication, and what is the plan before 2027.1?

9NetSuite vs SAP Business One for apparel

NetSuite has a native parent-and-child matrix item, a grid-entry SuiteApp, Advanced BOM with dated revisions, WIP and routing, and Outsourced Manufacturing, and it runs only as Oracle's cloud service; SAP Business One, per its partners, has no native colour-size matrix, so apparel users add a partner add-on or code each colour and size as its own item. Both handle batches or lots, units of measure, landed costs and production orders, and neither covers sampling, T&A, size-graded consumption or AQL out of the box. SAP Business One is SAP's ERP for small and mid-size companies, extended by partner add-ons.

Which should an apparel business choose?

Choose on the fit-gap, the partner and the business type. From practice, NetSuite tends to suit a brand, a wholesaler or a multi-entity group that wants one cloud ledger and accepts Oracle's release calendar; SAP Business One tends to suit a single-entity manufacturer or distributor that has found a strong apparel add-on and a partner who maintains it. In both, the size-colour question is answered before anything else: in NetSuite by the matrix design and its 2,000 ceiling, in B1 by the choice of add-on, which then has to follow every B1 upgrade. Read the SAP Business One chapter for its side in full, and the comparison table for the other ERPs.

SAP Business One facts come from SAP's help and from SAP partners, as listed in sources. The lack of a standard item matrix in B1 is stated by partners; confirm it on your B1 release with SAP.

10How should item types and materials be set up in NetSuite for apparel?

Set up NetSuite items by how each material is bought, stocked, costed and tracked: fabric and yarn as lot-numbered inventory items, trims and packaging as inventory items, finished garments as assembly matrix items (or inventory matrix items for a brand), and subcontract and import charges as service or other-charge items. In NetSuite the item record type, the costing method and the unit type are chosen per item, and two of them cannot be changed casually once the item is saved, so design the classes before the first import.

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 NetSuite item must follow them.

What each item class carries in NetSuite

Four choices sit on each NetSuite item record and shape the apparel design: the record type, the costing method, the unit type and whether the item tracks lots. Oracle's help states that the costing method cannot be changed after it is saved on the item record, and that Average is the default. Choose per class of item, and put the choice in the CSV import template so nobody picks it by hand (section 19).

• Record type. Inventory item, lot-numbered inventory item, assembly item (lot-numbered or not), non-inventory item, service item and other-charge item are the types an apparel account uses. Grid Order Management supports inventory and assembly items, including lot-numbered and serialised ones, and inventory and assembly matrix items; it does not support non-inventory, other-charge or service matrix items.
• Landed cost. An item takes a share of freight and duty only if its Track Landed Cost box is checked. Set it on fabric and imported trims.
• Units. With the Multiple Units of Measure feature, each item gets a unit type and, from it, a purchase unit, a stock unit, a sale unit and a consumption unit (section 12).

With operations on top: the style, its bill of materials by category and its consumption are built in the operations layer. NetSuite still needs the item classes above for everything it buys, stocks and values, because it holds stock value and the payables.

11How do you set up matrix items for sizes and colours in NetSuite?

Model the style as the parent matrix item and colour and size as matrix options; NetSuite creates a child item for each combination and tracks each one separately. Oracle's help puts it plainly: "The parent item doesn't appear on transactions. Only child items that show each option can be chosen on transactions." A matrix item in NetSuite is an item record family made of one parent and its subitems, one per option combination.

Two rules from Oracle's help shape every apparel design:

• The 2,000 ceiling. "The maximum number of the total combinations of matrix options is 2000." Oracle's CSV import guidance repeats it as a limit of 2,000 child matrix items per parent.
• No matrix of groups or kits. "Matrix items can't be created for groups or kits." A prepack sold by colour is therefore a separate item per colour (section 15).

Do the arithmetic before designing. A polo in 12 colours and 5 sizes is 60 children and never troubles the ceiling. A jean with many washes, 13 waists and 6 inseams reaches it quickly (Example 7). A style that must grow past the ceiling mid-season cannot, so the design has to leave room.

Changes after go-live are harder than they look. Oracle's import tips state that the CSV import cannot change matrix option values for existing child items, cannot move a child to a different parent and cannot change the matrix type of an existing item. Settle the option lists, the code pattern and which options sit on the matrix before the first import.

Naming and codes

Agree a code pattern before the first import, for example P2041-NVY-L for style, colour and size, and hold the buyer's own style number in a custom item field. Keep one matrix option list per size scale, so an "S" on a polo and an "S" on a bra band never share a value by accident. Integrations never link on the item name; they link on NetSuite's internal ID (section 34).

How does grid order entry work in NetSuite?

Grid entry in NetSuite comes from the Grid Order Management SuiteApp, which lets a user type quantities into a colour-by-size grid built from a grid template, on sales orders, purchase orders, transfer orders, quotes and inventory adjustments. A size/colour matrix, in this sense, is a grid with colours on one axis and sizes on the other, into which the quantity for each combination is typed. Oracle documents these limits:

With operations on top: styles, colourways and size breakdowns live in the operations layer, and NetSuite only needs the child items that are actually bought, stocked and invoiced. The matrix in NetSuite shrinks to what ships, which keeps every style far from the 2,000 ceiling.

12How do you convert kilograms to metres for fabric in NetSuite?

NetSuite converts units inside a unit type at a fixed conversion rate, so it can hold kilograms and metres for one fabric only at a nominal factor; a factor that changes with every roll needs a script or a system outside NetSuite. Knitted fabric is usually bought by weight and cut by length. The conversion depends on the fabric's weight per square metre (GSM) and its width, so it differs for every fabric and often for every roll.

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.

How NetSuite units work, from Oracle's help: with the Multiple Units of Measure feature on, a unit type groups related units. Each unit type has one base unit, whose conversion rate is locked at 1; every other unit has a conversion rate equal to the quantity of base units in one of it. An item gets one unit type, and from it a purchase unit, a stock unit, a sale unit and a consumption unit. For ordinary items the base unit must be the smallest unit. Lot-numbered items are more flexible: Oracle's help says their base unit does not have to be the smallest and they can use fractional quantities, with purchase, stock and sale in different units.

Because conversion rates live on the unit type, kg and m can share a unit type only if the business accepts one factor for everything that uses that type. That is the design decision.

Three workable designs

There are three workable ways to hold knit fabric in NetSuite, each with a trade-off. The designs are implementation practice, not Oracle guidance.

Pairs, dozens and packs

Count units convert cleanly inside one unit type. Buttons bought by the gross and issued by the piece, or socks knitted as singles and sold in pairs, sit in a count unit type whose base is the smallest unit (each or single) with gross at 144, dozen at 12 and pair at 2. A multi-pack of three pairs is a product, not a unit, and belongs with the prepacks in section 15.

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

13How do you track dye lots and fabric rolls in NetSuite?

Make fabric a lot-numbered inventory item, use each lot number as one dye lot, and require the lot on every receipt and every issue to production; record GSM, width and shade group in item number fields on the lot record. 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. Cutting must stay within one lot.

From Oracle's help, lot-numbered item records track the quantity and the specific cost of each lot as goods are bought and sold. The lot number record can hold an expiration date and notes, shows on-hand, on-order and available quantities per location, and can be extended with custom item number fields, which Oracle describes for information such as quality control procedures. Those fields can then be used to search for lots. Lot quantities are chosen on transactions through the Inventory Detail on each line. With Advanced Bin / Numbered Inventory Management, lots can also be tracked by bin.

Tracking each roll is a design choice, and the table below sets out the options from implementation practice.

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. NetSuite has no shade-band record; a shade group is an item number field on the lot, and the band itself sits in another system or a custom record.

Standard NetSuite lets a user pick any available lot on a work order issue. A rule that refuses two dye lots on one cut is a SuiteScript or workflow, or it lives in the operations layer.

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

14How do you handle size-dependent fabric consumption with NetSuite Advanced BOM?

NetSuite's Advanced Bill of Materials keeps BOMs as separate records with dated revisions, lets one BOM serve several assemblies and one assembly have several BOMs, and holds a component yield per line; fabric that grows with size therefore needs one BOM per size (or per size group), generated from a consumption table rather than typed. A bill of materials lists the components and quantities needed to make one unit of an assembly.

What Oracle's help says Advanced BOM does:

• The Advanced BOM record replaces the older Assembly/Bill of Materials record once the feature is enabled, and existing BOMs become read-only legacy records. Treat enabling it as a one-way decision and try it first in a sandbox.
• A BOM can have several revisions with effective start and end dates, used for stages such as an engineering BOM, a production BOM or a subcontracting BOM.
• Revisions cannot overlap. To add a revision starting on a date, first set the end date of the current revision to the day before.
• A component yield on the revision accounts for material loss in ordering and planning.
• One BOM can be used by several assemblies, an assembly can have several BOMs, and a default BOM can be set per assembly or per location.

For a garment, the children of the matrix differ in two ways. Colour changes components (navy thread and navy rib for navy children). Size changes quantities (more fabric for XL). One BOM per colour-size child is exact and heavy to maintain: 12 colours in 5 sizes is 60 BOMs for one style. Projects that go well generate those BOMs by CSV import or script from a consumption table (base size, grading per size, marker efficiency) and never type them.

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: they come from different people (CAD and lab), change for different reasons, and are argued about with different suppliers. NetSuite's component yield holds one loss factor per line; a second one is a custom field.

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 NetSuite. The approved PP round locks the style version for the order there. NetSuite needs no size-graded BOMs and no BOM revisions for garments at all.

15Should a prepack be an item group, a kit or an assembly in NetSuite?

Use an item group when the buyer orders a ratio pack but you want sales reported by size, a kit when the pack is priced and sold as one product with its own income account, and an assembly when packs are physically packed and stocked as cartons, because neither a group nor a kit is stocked as a packed unit. A prepack (or ratio pack) is a pack or carton holding sizes in a fixed ratio, for example 2 S, 5 M, 6 L, 5 XL and 2 XXL.

The differences Oracle documents between groups and kits:

The "Fits" row is our judgement from practice, not Oracle guidance. Test the choice against the buyer's EDI: an 856 ship notice that describes packs and a factory that stocks pieces must agree on what a pack is before go-live.

With operations on top: packs (ratio packs) are defined on the order in the operations layer, and packing and cartonisation happen there. NetSuite receives the dispatch in whatever item design finance chose for invoicing.

16How do you model cutting, sewing and finishing with NetSuite WIP, routings and Advanced Manufacturing?

Model the garment as an assembly with a manufacturing routing whose steps (cutting, sewing, finishing, packing) run at work centres with times and cost templates; with Manufacturing WIP, materials move through a WIP account from work order issue to completion to close. This gives a labour cost and operation progress per work order, but it does not balance a sewing line or track bundles.

What Oracle's help describes:

• Work orders track the quantities of an assembly to build and the components needed, through the statuses Planned, Released, In Process, Built and Closed. Without WIP, an assembly build records the production in one step.
• Manufacturing WIP splits production into three transactions: issue the work order (move materials to the work area), complete it (assemble and stock finished goods) and close it (reconcile variances). The WIP location on a line must match on all issue, completion and close transactions of the work order.
• Manufacturing Routing lists the steps to build an assembly. Work centres group labour resources for scheduling and cost tracking; cost templates assign labour and machine rates; operation tasks record what is done, when and how much is complete, and actual time against expected time. Costs post to WIP during assembly and move to the assembly asset account on completion.
• The Advanced Manufacturing SuiteApp adds a workbench, work instructions, material usage, capacity against demand, a scheduler for planned start and end times, mobile shop-floor data capture and performance reports. Oracle states its setup is done with NetSuite Professional Services.

What an operation time means 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 list each one as a routing step, or group them into a few steps per department. Grouping keeps operation tasks manageable; listing every operation gives a detailed cost but floods the task list.

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. NetSuite receives material issues for stock value and does not need routings or WIP for garments.

17Where do sampling, approvals and the T&A calendar live in a NetSuite project?

NetSuite has no record for garment samples, buyer approvals or a T&A calendar, so a NetSuite project either builds them as custom records with SuiteFlow or SuiteScript, uses a partner product, or keeps 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. The T&A calendar hangs on these dates. The typical failure is bulk fabric ordered, or cutting started, on the strength of an approval nobody can find.

What a custom sampling build in NetSuite must hold

If the project builds sampling inside NetSuite, it needs a small set of custom records (customrecord types) linked to the item and the sales order. The list below is the minimum we would design.

• A sample request per style and colourway, with its type (lab dip, strike-off, fit, size set, PP, TOP, shipment), linked to the parent matrix item.
• 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 BOM revision and spec version it approved.
• A block on the next step: a workflow that stops a bulk fabric purchase order or a work order release until the approval exists.
• T&A milestones that take their actual dates from the rounds, with a saved search per merchandiser each morning.

Each of these runs as SuiteFlow or SuiteScript under the governance limits in section 25, and each must be retested at every NetSuite release.

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

18How does NetSuite Outsourced Manufacturing work for CMT, embroidery, printing and washing?

NetSuite's Outsourced Manufacturing feature treats a subcontracted step as an outsourced work order for an assembly: it orders the components for the subcontractor, consumes them automatically when the goods come back, can move part-finished goods from one subcontractor to the next, and turns outsourced work orders into purchase orders through a daily consolidator. It is the closest native NetSuite match to CMT and job work.

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.

What Oracle's help documents:

• What it does. Creates subcontracting orders for assemblies from vendors, manages component ordering for the subcontractor, transfers half-finished assemblies to other subcontractors, and drop-ships or warehouses the finished assemblies. Components are consumed automatically on production.
• Prerequisites. Purchase Orders and Advanced Receiving (Transactions subtab of Enable Features), and Multi-Location Inventory, Assembly Items, Advanced Bill of Materials and Work Orders (Items & Inventory subtab). Outsourced Manufacturing itself is then enabled on the Items & Inventory subtab, under Setup > Company > Enable Features.
• Setup. An outsourcing location for the vendor, an outsourcing charge item, the vendor's outsourcing settings, and an Outsourcing subtab on the work order.
• The consolidator. The Outsourced Manufacturing Consolidator "aggregates outsourced work orders into purchase orders" and "is scheduled to run every day at 2:00 a.m. in your organization's time zone". It can be run at once with Run Consolidator Now from Setup > Manufacturing > Outsourced Manufacturing Management.

The consolidator timing matters on the floor. An outsourced work order created at 10:00 does not become a purchase order the printer can see until the next 2:00 a.m. run unless someone runs the consolidator by hand. Put that in the training and in the T&A lead time.

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. NetSuite shows stock at the subcontractor's outsourcing location and the purchase order status; the allowance, the reject reasons and the balance per buyer order are design work or a saved search to build.

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. NetSuite receives the subcontractor's purchase order and the payable, and does not need outsourced assemblies.

19How do you cost a garment in NetSuite, and why is the costing method a one-way choice?

NetSuite values stock by the costing method chosen on each item (Average, FIFO, LIFO, Group Average, Standard, Lot Numbered or Specific), and Oracle's help states that "you can't change the costing method after you save it on the item record", so the choice per item class is permanent. The garment costing sheet used to quote a buyer is built before any NetSuite item exists and usually lives outside NetSuite. 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.

Oracle lists these costing methods: Average (the default), FIFO, Group Average (one average cost across a group of locations), LIFO (not in the Australia edition), Specific (the cost of a serial number), Lot Numbered (the cost of a lot) and Standard (standard cost with variances between expected and actual). A wrong choice is fixed only by creating a new item and moving stock and history to it, which in an apparel account means new matrix children and new BOMs.

How do you configure landed cost in NetSuite for imported fabric and duty?

Turn on the Landed Cost feature, create landed cost categories (freight, clearing, duty, insurance, bank charges), check Track Landed Cost on each fabric and imported trim, and enter the charges on the item receipt or the vendor bill with a cost allocation method of Weight, Quantity or Value. 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.

From Oracle's help:

• Landed cost can be entered on item receipts and vendor bills. With Advanced Receiving on, allocation happens on the receipt.
• The allocation methods are Weight, Quantity and Value, and a transaction allocates with one method at a time.
• Only items with Track Landed Cost checked take a share.
• The Landed Cost Allocation per Line preference, under Setup > Accounting > Preferences > Accounting Preferences, Order Management subtab, lets you enter landed cost amounts per line, with several cost categories on the same line.

The one-method rule matters for apparel. Sea freight follows weight; clearing and bank charges usually follow value. On a single receipt with one method, one of them is allocated wrongly unless you use per-line allocation, or split the charges across transactions. For a factory in a free zone or under temporary admission, duty may be zero or suspended; agree the local reporting 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. NetSuite holds the landed cost that actually hit the receipts, for stock value, and the costing method still has to be chosen right for every item it values.

20Can NetSuite run quality control and AQL inspection for garments?

NetSuite's Quality Management SuiteApp creates specifications and inspections for incoming and outgoing shipments and shop-floor processes, with a statistical sampling workflow, but that workflow samples a fixed number or a fixed percentage and applies defect thresholds you enter; it does not look up ISO 2859-1 sample sizes from the lot size. 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.

From Oracle's help: a quality specification is a collection of related inspections measured against shop-floor processes and incoming and outgoing shipments. In the statistical sampling workflow, a setting decides whether the sampling rate is a number of samples or a percentage of the quantity to inspect, and Oracle notes that this is a one-time setting made when the template is created. Templates carry allowable critical, major and minor defects; above the limit, the inspection fails. Oracle's best-practice page suggests up to 40 data fields per inspection (30 as the optimum) and up to 35 inspections per specification (20 as the optimum).

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 receipt of 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. NetSuite sees the fulfilment only once it is cleared.

21How do you handle cartons, packing lists and shipping documents in NetSuite?

NetSuite fulfils sales orders through item fulfilments and prints packing slips and picking tickets, and the Grid Order Management SuiteApp adds grid printing on sales orders, packing slips and invoices; assorted cartons, buyer carton labels with SSCC codes and carton-level packing lists by dye lot usually need a partner product or custom work. An item fulfilment is NetSuite's record of goods leaving the warehouse against an order.

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. NetSuite receives the dispatch as an item fulfilment and raises the customer invoice.

22How does NetSuite handle currencies, customer deposits, letters of credit and chargebacks?

NetSuite handles foreign currencies and, with OneWorld, subsidiaries with their own base currency as standard, and takes advance payments as customer deposits against sales orders; letters of credit and reason-coded chargebacks need design, because we found no letter-of-credit record in NetSuite's help. Garment exporters usually sell in USD or EUR, buy some materials abroad and pay wages locally, so every order touches at least two currencies.

Multi-currency and OneWorld

Each subsidiary in OneWorld has a base currency that, per Oracle's help, cannot be changed after the subsidiary record is first saved; customers and vendors can transact in other currencies. Exchange-rate differences between an invoice and its payment are posted as realised gains or losses. For period-end revaluation of open foreign balances, confirm the process for your account with the partner and finance.

Customer deposits

A customer deposit in NetSuite records money received in advance for an order. Oracle's help describes it as a liability until the goods are delivered, with no effect on the customer's receivable balance; a Create Deposit button on the sales order records it, and it is applied against the invoice later. Oracle adds that the unapplied part of a deposit created from a sales order can be used as a credit on a customer payment only when the sales order is billed, cancelled or closed.

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. In NetSuite the credit number, amount, latest shipment date, expiry, presentation period and required documents become a custom record linked to the sales order, with a saved search or workflow that warns before the latest shipment date.

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 with a reason from a custom list, as a credit memo or a write-off to one account per reason, and keep the buyer's deduction notice attached. Without reason codes, nobody can tell whether the business loses money to labels or to lateness.

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

23Does NetSuite support e-invoicing and localisation for garment exporting countries?

NetSuite's Electronic Invoicing SuiteApp is a framework for sending and receiving e-documents; Oracle's help states it does not include native support for any country's requirements, which come from localisation SuiteApps for some countries or from templates you build. For each garment-exporting country, check Oracle's localisation list and a local partner before assuming compliance.

From Oracle's help: the SuiteApp handles outbound e-documents (generated and sent to customers, vendors or tax agencies) and inbound ones (received from vendors and turned into bills), using templates, with samples included. It is free for a single country; using e-documents across several countries needs a licence. Oracle lists dedicated localisation SuiteApps for countries including Malaysia, Israel, Mexico, India and Brazil.

We have not verified NetSuite coverage for Egypt, Turkey, Pakistan, Bangladesh, Vietnam, Morocco or Tunisia in this guide. For each, ask Oracle and the partner which statutory reports and e-invoice formats they have delivered for other clients, who maintains the template when the tax authority changes its rules, and test an e-invoice end to end in a sandbox before go-live. Egypt's e-invoicing, for example, involves registration with the Egyptian Tax Authority and signing of each invoice; confirm how a NetSuite account meets that before choosing NetSuite for an Egyptian subsidiary.

Factories in free zones or under temporary admission often report the import and re-export of materials to customs. NetSuite transactions carry the quantities, but the report format is local and usually a saved search or custom report.

24In what order should you configure NetSuite for a garment business?

Configure NetSuite for a garment business from the ledger outward: subsidiaries and base currencies first, then features, then units, matrix options and item classes, then locations, landed cost and manufacturing features, and only then the items, BOMs and open transactions. Each step depends on the one before it, and several cannot be undone once data exists: a subsidiary's base currency, an item's costing method, Advanced BOM and the matrix structure of an item.

Most features are switched on under Setup > Company > Enable Features, on subtabs such as Transactions and Items & Inventory; we name the subtab only where we checked it in Oracle's help. Labels move between releases, so check each on your account.

Two item-level choices decide most rework: the costing method (it cannot change after save) and Track Landed Cost (without it the item takes no freight or duty). Put both in the CSV import template, not in a person's memory.

25How is NetSuite extended for apparel: custom fields, SuiteFlow, SuiteScript or SDF?

NetSuite is extended through SuiteCloud: custom fields and custom records for data, SuiteFlow for approvals and simple rules without code, SuiteScript 2.x for logic such as unit conversion or AQL, and the SuiteCloud Development Framework (SDF) to keep all of it as versioned files deployed from sandbox to production. Everything runs inside Oracle's cloud under governance limits, so the design must respect them.

Custom fields and custom records

Custom fields carry a prefix by where they sit, which Oracle's naming conventions set out: custitem on items, custentity on customers and vendors, custbody on a transaction header and custcol on transaction lines. Custom records (IDs such as customrecord_…) hold things NetSuite has no record for, such as sample rounds or letters of credit. Item number fields on lot records hold GSM, width and shade group.

SuiteScript governance, and why it shapes apparel scripts

Every SuiteScript runs on a budget of usage units, set by script type, and a script that exceeds it stops. Oracle's limits per script type include:

For map/reduce scripts, Oracle also limits keys to 3,000 characters and values to 10 MB. The practical rule from projects: anything that touches every child of a matrix, or every BOM of a season, belongs in a map/reduce script, not in a user event script on save. A season rollover written as a user event runs out of units and leaves half the children updated.

SuiteFlow or SuiteScript?

SDF, sandboxes and releases

SuiteCloud Development Framework (SDF) keeps custom objects, such as custom records, forms, workflows and scripts, as XML and script files in a project. Oracle describes account customization projects for accounts you own, deployed to development, sandbox or production accounts, with a command-line interface that can automate validation and deployment. From practice: keep every apparel customisation in an SDF project under version control, deploy to a sandbox first, and rerun the end-to-end tests in section 28 in the sandbox before each NetSuite release reaches production.

26Which systems does a NetSuite apparel implementation integrate with?

A NetSuite apparel implementation typically connects to a PLM or tech-pack system, a shop-floor system, EDI with retailers, e-commerce and marketplaces, banks, and an operations layer; each connection needs one owner per field, links stored on NetSuite internal IDs, and a share of the account's concurrency budget. The table shows the usual source of truth for each kind of record, based on general practice.

Rules for every connection

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

• Link on NetSuite's internal ID, never on a document number or an item name a user can edit (section 34).
• One writer per field. If two systems can change the same quantity, one of them is wrong without knowing it.
• One owner per external ID. Oracle's help states that only a single integrated application should set external ID values for each record type.
• Show disagreements to a person. When the other system says something different, put it on a review list; never overwrite silently.
• Budget concurrency. Every integration draws on the same account limit; give each a share in Integration Governance and make receivers safe to call twice, because throttled calls get retried.

27How do you migrate apparel data into NetSuite?

Migrate only open and active apparel data into NetSuite (active styles as matrix parents and children, open orders, open purchase orders and stock by lot), load it in dependency order with the CSV Import Assistant and external IDs, and have each department head sign off the loaded figures. History stays in the old system or an archive.

Oracle's guidance on importing matrix items shapes the files: unlike the user interface, which creates children when options are chosen on the parent, a CSV import needs a separate line for each parent and each child, with a Matrix Type column (Parent Matrix Item or Child Matrix Item) and a Subitem of column naming the parent. Each child can carry its own pricing. The import cannot change option values on existing children, cannot move a child to another parent and cannot delete matrix options. Oracle also notes that the Units Type is set separately on parent and child during import, so map it for both.

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 NetSuite 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, lot by lot, 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 vendors and materials ("Navy Jersey 180", "Jersey 180 NVY").
• Retire styles with no order in two seasons.
• Give every fabric one unit type and one costing method, and every roll in stock its lot.
• Map old size labels to the new matrix option values, one scale at a time; check that no style will exceed 2,000 children.
• Split any "open" order line that is already partly delivered into delivered and open quantities.

External ID,Item Name/Number,Matrix Type,Subitem of,Colour,Size,Costing Method,Units Type
p2041,P2041,Parent Matrix Item,,,,Standard,Count
p2041_nvy_s,P2041-NVY-S,Child Matrix Item,P2041,Navy,S,Standard,Count
p2041_nvy_m,P2041-NVY-M,Child Matrix Item,P2041,Navy,M,Standard,Count
p2041_nvy_l,P2041-NVY-L,Child Matrix Item,P2041,Navy,L,Standard,Count
p2041_nvy_xl,P2041-NVY-XL,Child Matrix Item,P2041,Navy,XL,Standard,Count
p2041_nvy_xxl,P2041-NVY-XXL,Child Matrix Item,P2041,Navy,XXL,Standard,Count

External ID,Customer,Item,Quantity,Rate,Amount,Currency
so_p2041,BUYER-01,P2041-NVY-S,300,4.26,1278.00,USD
so_p2041,BUYER-01,P2041-NVY-M,750,4.26,3195.00,USD
so_p2041,BUYER-01,P2041-NVY-L,900,4.26,3834.00,USD
so_p2041,BUYER-01,P2041-NVY-XL,750,4.26,3195.00,USD
so_p2041,BUYER-01,P2041-NVY-XXL,300,4.26,1278.00,USD

Open PO:   navy jersey 180 GSM, 925 kg ordered, 0 kg received
Deposit:   USD 3,834.00 received against so_p2041
Stock:     buttons 15 mm navy, 9,504 each, location Main Store, no lot

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, deposits) 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 a NetSuite apparel implementation end to end?

Test a NetSuite apparel implementation in a sandbox with end-to-end scenarios that follow one real order from the buyer's PO to cash, run by the key users on 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. Rerun the same scenarios in the sandbox before every NetSuite release reaches production.

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 panels sent out, panels returned and panels lost add up, using Outsourced Manufacturing. The polo's chest logo is embroidered outside, with a 1% allowance.

The reject reasons in step 4 and the allowance check in step 5 are custom fields or a saved search; Outsourced Manufacturing consumes components but does not hold a loss allowance.

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 field and check from section 25; standard NetSuite has no quantity-tolerance field on a sales order.

29How should you train a garment business's staff on NetSuite?

Train each role only on the NetSuite centres, forms and saved searches it will use, on the business's own styles and orders, and have key users teach their colleagues; build role-specific dashboards so each person opens NetSuite on their own work. A merchandiser does not need the accounting menus, and a floor supervisor needs one screen that works, not a NetSuite role.

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. Remember that the Grid Order Management form is English only, so plan grid training in English with local-language notes where teams work in another language.

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 NetSuite forms on the floor, expect the data never to arrive.

30What does a NetSuite cut-over plan look like for a garment business?

A NetSuite cut-over plan is a day-by-day list of the steps that move the business from the old system to NetSuite: freeze, final imports, stock count, 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 sandbox before the real weekend, and time the imports there, because a matrix of thousands of children takes longer to load than people expect.

31When should a garment business go live on NetSuite, and how long is hypercare?

Go live between seasons, in the lowest-volume weeks, away from year-end and away from a NetSuite release weekend, and keep the partner in close support until at least the first month-end close is done in NetSuite. 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 month-end of the financial year and any audit. Check Oracle's release schedule for your account and keep go-live clear of the upgrade of your production account.
• Parallel running. A short, bounded parallel run of the books can help finance compare figures. Running the whole business 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 NetSuite is complete.
• Issue log. Keep one list: date, who, what happened, severity, owner, status. Review it daily in the first two weeks. Watch script errors and concurrency errors in the logs as closely as user issues.
• Exit criteria. Hypercare ends when the month-end closes on time, no issue blocks shipping or invoicing, and the administrator and key users handle first-line questions without the partner.

32What are the most common mistakes when implementing NetSuite for apparel?

The most common mistakes in apparel NetSuite projects are a matrix design that hits the 2,000-combination ceiling, the wrong costing method on items (it cannot be changed), expecting the Grid Order Management SuiteApp to work everywhere, heavy scripts that break governance or concurrency limits, the wrong item type for prepacks, and treating the AFA edition as a complete apparel solution. The list below comes from implementation practice; each point links to the Oracle fact behind it.

1. A matrix that hits 2,000.Too many options on one parent, typically length or inseam; the next colour cannot be added mid-season (section 11).
2. Grid limits discovered late.No grid on mobile, English only, multi-grid on sales orders only, one currency per grid order, form customisations not on the grid form.
3. The wrong costing method.It cannot be changed after the item is saved; fixing it means new items (section 19).
4. One kg-to-metre factor for every fabric.Stock value looks right while the cutting room runs short (section 12).
5. One BOM shared across sizes.Advanced BOM makes it easy; fabric runs short on large sizes (section 14).
6. Dye lots not enforced at issue.Standard NetSuite lets a user pick any lot; shade differences are found at final inspection.
7. Prepacks on the wrong item type.A kit or group where packed cartons are stocked, or an assembly where SKU sales reporting was needed (section 15).
8. Season-wide scripts on save.A user event script with 1,000 usage units updating a whole matrix; use map/reduce.
9. Concurrency spent before go-live.E-commerce, EDI, iPaaS and the floor system share one account limit; nobody budgeted it (section 34).
10. New integrations on SOAP or token-based authentication.Oracle is closing both; build on REST with OAuth 2.0.
11. Treating the AFA edition as complete.It configures NetSuite for the industry; tech packs, cut planning, sampling and AQL still need a partner product or an operations system.
12. Outsourcing PO timing.The consolidator runs at 2:00 a.m.; the subcontractor gets the purchase order a day later than the planner expects.

The 15 general failure modes, and how each shows up in NetSuite

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

33What must be decided before a NetSuite apparel go-live?

Decide the subsidiary structure and base currencies, the matrix design against the 2,000 ceiling, the costing method per item class, the unit design for every fabric, the lot and bin rules, whether to enable Advanced BOM and WIP, the prepack item type, the concurrency budget, and which system owns sampling, T&A and floor capture before go-live, because each is expensive or impossible to change once transactions exist. The full list:

• Subsidiaries and each subsidiary's base currency (cannot change after first save).
• The matrix parent level per category and the options on each; the largest realistic season checked against 2,000.
• The costing method per item class (cannot change after save), and which items track landed cost.
• The unit type for every fabric and yarn, and how kg becomes metres.
• Lot, bin or custom record for rolls; which item number fields are mandatory at receipt.
• Advanced BOM (a one-way switch), BOM per size or per group, and how BOMs are generated.
• Manufacturing WIP and Routing, or one-step assembly builds.
• Item group, kit or assembly for each kind of prepack.
• Outsourced Manufacturing for subcontract steps, and who runs the consolidator by hand when needed.
• Which system owns sampling, T&A, planning, floor capture and quality: NetSuite custom records, a partner product 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: class, department or custom segment.
• The service tier, SuiteCloud Plus licences and each integration's concurrency share.
• REST with OAuth 2.0 for every new integration, and the plan for any existing SOAP or TBA integration.
• Who owns sandbox release testing after the partner leaves.

34Which NetSuite API should an apparel integration use, and what are its limits?

Build every new NetSuite integration on SuiteTalk REST web services (or RESTlets) with OAuth 2.0, store NetSuite's internal ID as the link, and plan inside the account's concurrency limit, because Oracle is retiring SOAP web services and token-based authentication on published dates. SuiteTalk is the name of NetSuite's web-services family, and a RESTlet is a SuiteScript that exposes a custom REST endpoint.

What does Oracle say about SOAP and token-based authentication?

Oracle's help is explicit on both, and the dates matter to any apparel business with an older connector:

• SOAP. "The 2025.2 SOAP endpoint is the last planned SOAP endpoint." "With the 2027.1 release, only the 2025.2 endpoint will be supported. With the 2028.2 release, SOAP will no longer be available in NetSuite and existing SOAP integrations with NetSuite will stop working." Oracle adds: "All newly built integrations should use REST web services with OAuth 2.0 for authentication."
• Token-based authentication (TBA). "Starting in NetSuite 2027.1, you will no longer be able to create new integrations that use TBA for SOAP and REST web services, and RESTlets." Support for existing TBA integrations ends later, "tentatively NetSuite 2028.2", excluding SuiteAnalytics Connect (ODBC/JDBC). Oracle's advice is to move affected integrations to OAuth 2.0. Some partners quote other dates; we quote Oracle.

Authentication, endpoints and identifiers

Internal ID versus document number. A purchase order has an internal ID, a number NetSuite assigns and users do not edit, and a document number (the transaction's tranid) that people see and that numbering settings or users can change. The same goes for items: the internal ID is stable, the item name is text. An integration that stores "PO-00457" breaks the day someone renumbers; one that stores the internal ID does not. Use the external ID as the idempotency key your side sets, and the internal ID as the link you store.

Concurrency: the budget every integration shares

NetSuite limits how many web-service and RESTlet requests an account runs at the same time. Oracle's published base limits are 5 (Standard), 15 (Premium), 20 (Enterprise) and 20 (Ultimate) on the current service tiers, with legacy tiers listed separately, and each SuiteCloud Plus licence adds 10; development and partner accounts stay fixed at 5. A limit per integration can be set under Setup > Integration > Integration Management > Integration Governance, and Oracle notes that allocating to one application reduces what the others can use, that at least one unit always stays unallocated, and that as a best practice a single account limit without individual limits is preferable. Oracle's concurrency page describes SOAP web services and RESTlets; confirm with Oracle how REST web-service calls count on your account.

Push or pull?

Pulling is the dependable baseline: a scheduled job queries changes with SuiteQL or a saved search on the last-modified date and processes them in order. Pushing from NetSuite uses a user event SuiteScript that calls out when a record changes; it is faster, but it runs inside the user's save and its governance, so keep it small and let a scheduled job catch anything it missed. iPaaS products (Oracle NetSuite Connector for commerce and marketplaces, and third-party platforms) sit in between; each still draws on the same concurrency.

POST /api/v1/erp/po-status
Idempotency-Key: netsuite-po-48213-created

{"rows": [{"request_ref": "PR-1042",
           "erp_po_id": "48213",
           "erp_po_number": "PO-00457",
           "status": "Pending Receipt",
           "date": "2026-10-21"}]}

For a business that does not want to build an integration, the same exchange works as a file exchange: MerchandiserOS produces the purchase requests as a file, the NetSuite team imports them with the CSV Import Assistant, and a saved-search export of PO numbers and statuses comes back the same way. Every inbound change is still approved by a person. The API guide at /developers describes both.

35If you don't manufacture: brands, buying agents and own-label retailers on NetSuite

A business that designs, sources or sells garments without making them should use NetSuite for matrix items, purchase orders to factories, landed cost, vendor bills and payments, wholesale sales orders, customer deposits and currencies, and should skip the manufacturing modules entirely. What NetSuite handles poorly for them is the work around the purchase order: development and sampling with many factories, T&A across factories, following production that happens elsewhere, inspections at the vendor, and one status per order across many factories and buyers. This is where NetSuite as an ERP for fashion brands is strongest, and where the gap is least obvious.

Who is this Part for?

Three kinds of apparel business make nothing themselves, and each uses NetSuite differently.

What does a clothing brand need from NetSuite, and what should it skip?

A brand needs the purchasing, landed cost, stock, sales and finance halves of NetSuite, and none of the manufacturing half. As an ERP for clothing brands, NetSuite's relevant pieces are these:

Skip: assembly items, work orders, Advanced Bill of Materials, Manufacturing WIP and Routing, the Advanced Manufacturing SuiteApp and Outsourced Manufacturing. A brand that buys finished garments has no BOM to maintain and no WIP to value, and each of those features adds setup, licences and release testing for nothing. The exception is a brand that supplies fabric or trims to its CMT factories: it needs purchase orders for those materials, a location per factory for the goods it has sent, and a reconciliation of what came back as garments, which is a design question for finance, not a reason to switch on manufacturing.

What does a buying agent need?

A buying house needs commission accounting and little else from an ERP: a commission invoice to the buyer, usually a percentage of the FOB value of what shipped, in the buyer's currency. In NetSuite that is an invoice with a service item for the commission, with no inventory items, no goods purchase orders and no goods receivables. The agent's real work, following orders across factories, sits outside any ERP; buying house ERP and sourcing agent software searches usually end at tools for that follow-up, not at accounting.

What does an own-label retailer need?

For private label sourcing, the retailer needs what a brand needs on the purchasing side, plus a retail system for stores. Store operations, POS, allocation and open-to-buy are a separate project, in NetSuite (Oracle lists a SuiteSuccess edition for retail) or in another retail system; this guide does not cover them.

What does NetSuite handle poorly for brands and agents?

NetSuite records the purchase order to the factory well; it does not follow the order at the factory. Five things stay open for a business that makes nothing itself:

• Development and sampling with many factories. Tech packs, lab dips, strike-offs and PP samples, round by round, with several factories quoting and sampling the same style. NetSuite has no record for any of it (section 17).
• T&A across factories. A calendar per order, worked back from the ex-factory date, with milestones owned by people at different factories.
• Following production that happens outside. Cutting, sewing and packing at the factory are invisible in NetSuite until the goods are received; Outsourced Manufacturing is built for subcontracted assemblies inside a manufacturer, not for a brand following finished-goods factories.
• Inspections at the vendor. Final AQL at the factory before shipment, at the buyer's level, with the result gating the goods leaving. NetSuite's Quality Management SuiteApp is built around inspections on the account's own receipts and operations.
• One status per order across factories and buyers. A buying agent with twenty factories and eight buyers needs one view of where every order stands. Saved searches over purchase orders show what was ordered and received, not what is happening in between.

How does the MerchandiserOS model work for a brand or agent?

MerchandiserOS runs the work around the order and NetSuite keeps the books. For a brand, buying agent or own-label retailer, 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. NetSuite keeps purchase orders as the financial record, landed cost, stock value, invoicing, payments, deposits, currencies and tax. MerchandiserOS has workspace set-ups for a Brand and a Buying agent, so neither sees factory screens it does not need. Retail back-office work, such as stores, POS, allocation and open-to-buy, is outside MerchandiserOS's scope.

For the other side of the same order, see Parts 3 to 7, and for how other ERPs serve brands, the Business Central chapter and the apparel-specific ERP chapter.

·Glossary of apparel and NetSuite terms

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

Advanced BOM

NetSuite's Advanced Bill of Materials feature: BOMs as separate records with dated revisions, shared across assemblies, with a default per assembly or location.

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.

Assembly item

A NetSuite item built from components on a BOM; in apparel, the garment or an intermediate such as a printed panel.

BOM revision

A version of a NetSuite BOM with effective start and end dates; revisions of one BOM cannot overlap.

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.

Component yield

A value on a NetSuite BOM revision line that accounts for material loss in ordering and planning.

Consolidator

The Outsourced Manufacturing job that turns outsourced work orders into purchase orders, daily at 2:00 a.m. or on demand.

Cost template

A NetSuite record of labour and machine rates used by routing steps to cost production.

Customer deposit

A NetSuite record of money received in advance for a sales order, held as a liability and applied to the invoice.

Cut-over

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

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.

External ID

An identifier set by an integrating application on a NetSuite record, used with the eid: prefix for create-or-update calls.

FOB

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

Grid Order Management

An Oracle SuiteApp for colour-by-size grid entry on sales, purchase and transfer orders, quotes and inventory adjustments.

GSM

Grams per square metre: the weight of fabric.

Hypercare

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

Internal ID

The identifier NetSuite assigns to a record; the stable key an integration should store.

Item group, kit

NetSuite items that sell several members together; a group is priced from its members, a kit has its own price levels and income account.

Item number field

A custom field on NetSuite's lot or serial number record, used here for GSM, width and shade group.

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 warehouse 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.

Lot-numbered item

A NetSuite item whose stock is tracked by lot number, with quantity and cost per lot.

Marker efficiency

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

Matrix item

A NetSuite item family of one parent and a child per option combination, such as colour and size; at most 2,000 combinations.

OneWorld

The NetSuite edition for several subsidiaries, each with its own base currency.

Outsourced Manufacturing

The NetSuite feature for subcontracted assemblies: components sent to subcontractors, automatic consumption, moves between subcontractors.

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.

Ratio pack

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

RESTlet

A SuiteScript that exposes a custom REST endpoint on a NetSuite account.

SDF

SuiteCloud Development Framework: file-based projects for NetSuite customisations, deployed to sandbox and production.

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 enter or show order quantities for each combination.

Strike-off

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

SuiteApp

An application installed into a NetSuite account, from Oracle or a partner.

SuiteQL

NetSuite's SQL-based query language, available through REST web services.

SuiteScript

NetSuite's JavaScript-based scripting, run under usage-unit governance per script type.

SuiteSuccess

NetSuite's industry configurations, including an Apparel, Footwear and Accessories edition.

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.

UCP 600

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

Unit type

A NetSuite group of related units with a base unit and fixed conversion rates.

WIP (Manufacturing WIP)

The NetSuite feature that splits production into work order issue, completion and close through a WIP account.

More terms across all ERPs are in the guide glossary, and the method behind every chapter is in the methodology.

·Checklists: a NetSuite apparel 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 buyer and each subsidiary: CMT, full package, brand, agent or own label.
• One decision owner named for each area, and an in-house NetSuite administrator.
• One workshop per department, walking a real recent order.
• All 52 fit-gap lines answered with evidence, decision and owner.
• Architecture decided: what NetSuite owns, what runs in an operations layer.
• Edition, SuiteApps, OneWorld, service tier and concurrency confirmed against the fit-gap.

Design

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

• Subsidiaries and base currencies fixed.
• Matrix parent level and options per category; largest season checked against 2,000.
• Costing method per item class; Track Landed Cost on imported items.
• Unit type per fabric and yarn; kg-to-metre approach chosen.
• Lot as dye lot; item number fields; roll design (lot, bin or none).
• Advanced BOM on or off; BOM per size and how BOMs are generated.
• Prepack item type per kind of pack.
• WIP and routings, or one-step builds; Outsourced Manufacturing for subcontract steps.
• Inspection points, AQL plan source and override rights.
• Carton rules and buyer documents per buyer.
• Currencies, deposits, LC records, chargeback reasons, e-invoicing.

Build, data and testing

Build, migration and testing are complete when every item below is proven in the sandbox.

• Features enabled in dependency order; one-way switches signed off.
• Scripts inside governance limits; bulk work on map/reduce; all customisation in SDF projects.
• Integrations on REST with OAuth 2.0, linked on internal IDs, each with a concurrency share.
• Migration imported in order, parents before children, 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 business's own orders.
• Cut-over rehearsed once in full in a sandbox, imports timed.
• Go-live date between seasons, away from year-end, audits and the account's release upgrade.
• Go or no-go point and fall-back defined.
• Hypercare runs at least until the first month-end close in NetSuite; release testing owned in-house.

·Sources

Oracle NetSuite online help pages were checked on 26 September 2026. NetSuite is updated twice a year, so check each page against your account's release.

1. NetSuite help, Matrix Items (2,000 combinations; parent not on transactions; no matrix for groups or kits) — docs.oracle.com
2. NetSuite help, Tips for Matrix Items Import — docs.oracle.com · Importing Matrix Options for Items — docs.oracle.com
3. NetSuite help, Grid Order Management — docs.oracle.com · Limitations of Grid Order Management — docs.oracle.com
4. NetSuite help, Item Groups and Kits/Packages — docs.oracle.com
5. NetSuite help, Advanced Bill of Materials — docs.oracle.com · BOM revisions — docs.oracle.com
6. NetSuite help, Lot Numbered Items — docs.oracle.com · Serial and Lot Inventory with Multiple Units of Measure — docs.oracle.com
7. NetSuite help, Multiple Units of Measure — docs.oracle.com · Setting Up Units of Measure — docs.oracle.com
8. NetSuite help, Costing Methods — docs.oracle.com
9. NetSuite help, Landed Cost Overview — docs.oracle.com · Entering Landed Cost on a Transaction — docs.oracle.com · Landed Cost Allocation per Line — docs.oracle.com
10. NetSuite help, Assembly Work Orders — docs.oracle.com · Manufacturing WIP — docs.oracle.com · Manufacturing Routing and WIP — docs.oracle.com
11. NetSuite help, Advanced Manufacturing — docs.oracle.com
12. NetSuite help, Outsourced Manufacturing — docs.oracle.com · Setup — docs.oracle.com · Consolidator — docs.oracle.com
13. NetSuite help, Quality Management User Guide — docs.oracle.com · Statistical Sampling Workflow — docs.oracle.com · Best Practices — docs.oracle.com
14. NetSuite help, SuiteSuccess (editions incl. Apparel, Footwear and Accessories) — docs.oracle.com · NetSuite apparel page — netsuite.com
15. NetSuite help, Multiple Currencies in OneWorld — docs.oracle.com · Setting a Base Currency — docs.oracle.com
16. NetSuite help, Customer Deposits — docs.oracle.com
17. NetSuite help, Demand Planning — docs.oracle.com
18. NetSuite help, Electronic Invoicing Overview — docs.oracle.com · Availability and licence — docs.oracle.com
19. NetSuite help, SuiteScript governance — docs.oracle.com · Script Type Usage Unit Limits — docs.oracle.com
20. NetSuite help, Conventions for Naming Custom Objects — docs.oracle.com
21. NetSuite help, SuiteCloud Development Framework — docs.oracle.com · Account Customization Projects — docs.oracle.com
22. NetSuite help, SOAP web services deprecation — docs.oracle.com
23. NetSuite help, Token-based Authentication deprecation — docs.oracle.com
24. NetSuite help, OAuth 2.0 Client Credentials Flow — docs.oracle.com · Setup — docs.oracle.com
25. NetSuite help, Concurrency governance limits — docs.oracle.com · Per-integration limits — docs.oracle.com
26. NetSuite help, Executing SuiteQL Queries Through REST Web Services — docs.oracle.com · Using External IDs (REST) — docs.oracle.com · Using the Upsert Operation — docs.oracle.com
27. NetSuite help, REST API Browser and record IDs (Purchase Order, Inventory Item) — docs.oracle.com · docs.oracle.com · docs.oracle.com
28. NetSuite help, Oracle NetSuite Connector — docs.oracle.com
29. SAP Business One: Service Layer v1 and v2 — help.sap.com · Integration Framework — help.sap.com · item variants per partners — sana-commerce.com · emerging-alliance.com
30. ISO 2859-1, Sampling procedures for inspection by attributes — iso.org
31. AQL tables and acceptance numbers — qima.com · tetrainspection.com · inspection levels: qualityinspection.org
32. UCP 600, documentary credits — uscib.org · tradefinanceglobal.com
33. EDI transaction sets — 1edisource.com · celigo.com

Corrections. NetSuite is released twice a year, and a feature boundary, a limit or a deadline can move in a single release. If you find a statement here that your account contradicts, report a correction with the release and the help page you checked; we correct the guide and note the change and its date at the top of this section. We re-check the NetSuite facts in this chapter at least once a year and after each NetSuite release that touches items, manufacturing or web services.

Oracle and NetSuite are registered trademarks of Oracle and/or its affiliates, used here only to name the products. This guide is not endorsed by Oracle. SAP and SAP Business One are trademarks of SAP SE. Other product names belong to their owners. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.