ERP Leading Practice for Apparel, Footwear and Accessories
Back to Blog

ERP Leading Practice: Apparel, Footwear, Accessories

Thirteen NetSuite process areas for apparel, footwear and accessories brands, each with its flow, rules and a copy-ready skill file.
Oracle NetSuite
November 3, 2026
Written by: Jack Tadros

ERP Leading Practice for Apparel, Footwear and Accessories

An apparel brand sells the same SKU to a department store buying at wholesale, to a shopper on its website, and across the counter in its own store, and the edition treats those three channels differently at almost every step: how the order arrives, how it is paid, how it comes back and how it is refunded. The one place the channels meet is allocation. When stock is short, a rule has to decide which channel's order gets it, and in this edition that rule is configured rather than improvised. This is the leading practice reference for apparel, footwear and accessories brands: every process area, the flow it follows, the rules that govern it, and a copy-ready skill file for each one.

How to Use This

Each process area below carries three things. A flow, which is the sequence the process actually runs in. A short set of rules specific to apparel, footwear and accessories brands rather than generic ERP advice. And a skill file you can copy straight out of the page, written as markdown so it can be handed to an AI assistant, dropped into a project repository, or used as the basis for a design document.

The skill files are deliberately short. They are checklists for people who already know the domain, not tutorials. Each one names the roles that own the process, the flow, the rules, what to verify before go-live, and the failure modes that recur.

Methodology note. This reflects the Apparel, Footwear and Accessories Standard and Premium editions as applied by Azdan across its NetSuite delivery in the UAE, Saudi Arabia, and Egypt. Module availability differs by edition and license, so confirm against your own before treating any rule as available. Where a point is a recommendation from delivery experience rather than a documented rule, it is labeled as one.

The 13 Process Areas

Item Management → Inventory and Warehouse → Planning and Replenishment → Procure to Pay → Return to Debit → Lead to Quote → Order Management → Allocation and Commitment → Fulfillment and Billing → Return to Credit → Marketing and Promotions → Customer Service → Financial Management
Process areaPrimary ownerWhat it covers
Item ManagementBuyer/PlannerMatrix items, attributes, hierarchy and pricing.
Inventory and WarehouseWarehouse ManagerLocations, statuses, counts and adjustments, for warehouses, 3PLs and stores alike.
Planning and ReplenishmentBuyer/PlannerPlans built outside the system and executed inside it, from reorder points to store transfers.
Procure to PayBuyer/PlannerBuying seasonal stock in volume, receiving it through inspection, and landing its true cost.
Return to DebitBuyer/PlannerVendor returns and credits, most often for goods damaged on arrival.
Lead to QuoteSales RepresentativeWholesale selling: teams, territories, quotas, opportunities and quotes.
Order ManagementSales RepresentativeThree channels, three ways in: wholesale orders keyed on the grid, web orders by integration, store sales as a nightly summary.
Allocation and CommitmentSales & Operations ManagerWhere the channels compete for the same stock.
Fulfillment and BillingWarehouse AssociateShipping and invoicing, which also split by channel.
Return to CreditCustomer Service RepresentativeCustomer returns by channel, with exchanges handled as a return plus a new order.
Marketing and PromotionsSales & Operations ManagerCampaigns and promotions, with one decision first: which system owns the promotion engine.
Customer ServiceCustomer Service ManagerCases from web forms, email and phone, routed by rule and linked to the orders and returns they concern.
Financial ManagementControllerStructure, intercompany and the close, where the choice of intercompany method decides how much work every transfer creates.
Apparel, footwear and accessories process areas: thirteen NetSuite processes from item management to financial management, each with its flow

1. Item Management

Matrix items, attributes, hierarchy and pricing. The matrix structure chosen here shapes the product pages, the grid templates and every count that follows.

Roles: Buyer/Planner, Merchandising Manager, Accounting Manager

Process flow

Define item options → Create matrix styles by CSV → Assign hierarchy and attributes → Set costing and price levels → Map landed cost template

Leading practice rules

  • Use matrix items for anything sold in options, structured Style, Color, Size. Items without options are inventory items.
  • Define every option before creating matrix items. Keep option lists under 500 values; the hard limit is 1,000, and a parent takes at most 2,000 child SKUs.
  • Create matrix items by CSV import, not the matrix import assistant.
  • In SuiteCommerce, a Style parent puts color choices on one product page; a Style-Color parent gives each color its own page.
  • Use the merchandise hierarchy for reporting, and attributes such as season, collection, year and NRF color code to segment pricing and promotions.
  • Average costing is recommended, chosen before item creation since it cannot be changed. Keep an original price field so markdowns are taken from it.

Skill file: Item Management

---
name: afa-item-management
description: NetSuite leading practice for Item Management in apparel, footwear and accessories brands
---

# Item Management - Apparel, Footwear and Accessories

## Roles
Buyer/Planner, Merchandising Manager, Accounting Manager

## Process flow
Define item options → Create matrix styles by CSV → Assign hierarchy and attributes → Set costing and price levels → Map landed cost template

## Leading practice rules
- Use matrix items for anything sold in options, structured Style, Color, Size. Items without options are inventory items.
- Define every option before creating matrix items. Keep option lists under 500 values; the hard limit is 1,000, and a parent takes at most 2,000 child SKUs.
- Create matrix items by CSV import, not the matrix import assistant.
- In SuiteCommerce, a Style parent puts color choices on one product page; a Style-Color parent gives each color its own page.
- Use the merchandise hierarchy for reporting, and attributes such as season, collection, year and NRF color code to segment pricing and promotions.
- Average costing is recommended, chosen before item creation since it cannot be changed. Keep an original price field so markdowns are taken from it.

## Check before go-live
- [ ] Parent level agreed with the eCommerce team
- [ ] Option lists sectioned to stay under 500 values

## Known failure modes
- Matrix items built through the import assistant, leaving incomplete SKUs

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

2. Inventory and Warehouse

Locations, statuses, counts and adjustments, for warehouses, 3PLs and stores alike.

Roles: Warehouse Manager, Warehouse Associate, Supply Chain Manager

Process flow

Set up locations → Receive into inspection → Assign inventory status → Count → Adjust → Write off damaged goods

Leading practice rules

  • Keep stores as inventory locations alongside warehouse, 3PL, in-transit, inspection and quarantine locations.
  • Capture inventory status at receipt, with unavailable statuses such as Damaged, and change it with an inventory status change.
  • Use the Inventory Count transaction for counts and shrinkage; full counts quarterly in the warehouse and monthly in stores are common.
  • Use Inventory Adjustment, not the worksheet, for FIFO or LIFO, binned, and lot or serial items.
  • Write off damaged goods monthly from an unavailable status, once no vendor return is pending.
  • Record 3PL receipts, fulfillments and count adjustments in the system.

Skill file: Inventory and Warehouse

---
name: afa-inventory-and-warehouse
description: NetSuite leading practice for Inventory and Warehouse in apparel, footwear and accessories brands
---

# Inventory and Warehouse - Apparel, Footwear and Accessories

## Roles
Warehouse Manager, Warehouse Associate, Supply Chain Manager

## Process flow
Set up locations → Receive into inspection → Assign inventory status → Count → Adjust → Write off damaged goods

## Leading practice rules
- Keep stores as inventory locations alongside warehouse, 3PL, in-transit, inspection and quarantine locations.
- Capture inventory status at receipt, with unavailable statuses such as Damaged, and change it with an inventory status change.
- Use the Inventory Count transaction for counts and shrinkage; full counts quarterly in the warehouse and monthly in stores are common.
- Use Inventory Adjustment, not the worksheet, for FIFO or LIFO, binned, and lot or serial items.
- Write off damaged goods monthly from an unavailable status, once no vendor return is pending.
- Record 3PL receipts, fulfillments and count adjustments in the system.

## Check before go-live
- [ ] Inspection and quarantine locations at every receiving site

## Known failure modes
- 3PL counts never brought back into the system, so available quantities drift

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

3. Planning and Replenishment

Plans built outside the system and executed inside it, from reorder points to store transfers.

Roles: Buyer/Planner, Supply Chain Manager, Merchandising Manager

Process flow

Plan externally → Import plan → Set reorder points → Order items → Transfer to stores → Build if needed

Leading practice rules

  • Build season plans and open-to-buy outside the system and import them. Demand Planning, Premium only, plans by SKU not style, handles one season, and needs six months of sales.
  • Set reorder points, preferred stock, lead times and safety stock for mid-season replenishment.
  • The Supply Chain Control Tower works at SKU level, not style.
  • Use transfer orders between warehouses and stores, and inventory transfers between virtual locations such as inspection and quarantine.
  • Store allocation is a push model with no store allocation module: calculate it externally and import the results as transfer orders.
  • Keep work orders to low-volume, bespoke builds, since they run per SKU.

Skill file: Planning and Replenishment

---
name: afa-planning-and-replenishment
description: NetSuite leading practice for Planning and Replenishment in apparel, footwear and accessories brands
---

# Planning and Replenishment - Apparel, Footwear and Accessories

## Roles
Buyer/Planner, Supply Chain Manager, Merchandising Manager

## Process flow
Plan externally → Import plan → Set reorder points → Order items → Transfer to stores → Build if needed

## Leading practice rules
- Build season plans and open-to-buy outside the system and import them. Demand Planning, Premium only, plans by SKU not style, handles one season, and needs six months of sales.
- Set reorder points, preferred stock, lead times and safety stock for mid-season replenishment.
- The Supply Chain Control Tower works at SKU level, not style.
- Use transfer orders between warehouses and stores, and inventory transfers between virtual locations such as inspection and quarantine.
- Store allocation is a push model with no store allocation module: calculate it externally and import the results as transfer orders.
- Keep work orders to low-volume, bespoke builds, since they run per SKU.

## Check before go-live
- [ ] Plan import format agreed before go-live

## Known failure modes
- Demand Planning switched on for multi-season planning it cannot do

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

4. Procure to Pay

Buying seasonal stock in volume, receiving it through inspection, and landing its true cost.

Roles: Buyer/Planner, Supply Chain Manager, Warehouse Associate, A/P Analyst

Process flow

Enter PO on the grid → Approve → Bulk or master PO → Inbound shipment → Receive into inspection → 3-way match → Actual landed cost → Pay

Leading practice rules

  • Enter purchase orders on the grid; above 500 lines, or for many orders at once, import them.
  • For store allocations, use bulk purchase orders: transfer orders create the demand that receipt fills, or a scripted roll-up of child orders keeps 3-way match intact.
  • Receive into a virtual inspection location, and use Quality Management for complex inspections.
  • Create an inbound shipment per ASN. Update PO quantities before taking ownership, and close the container on a short ship.
  • Estimated landed cost posts at receipt. Clear non-material variances with a journal and material ones with an inventory revaluation.
  • Review landed cost templates no more than quarterly, after quarter close.

Skill file: Procure to Pay

---
name: afa-procure-to-pay
description: NetSuite leading practice for Procure to Pay in apparel, footwear and accessories brands
---

# Procure to Pay - Apparel, Footwear and Accessories

## Roles
Buyer/Planner, Supply Chain Manager, Warehouse Associate, A/P Analyst

## Process flow
Enter PO on the grid → Approve → Bulk or master PO → Inbound shipment → Receive into inspection → 3-way match → Actual landed cost → Pay

## Leading practice rules
- Enter purchase orders on the grid; above 500 lines, or for many orders at once, import them.
- For store allocations, use bulk purchase orders: transfer orders create the demand that receipt fills, or a scripted roll-up of child orders keeps 3-way match intact.
- Receive into a virtual inspection location, and use Quality Management for complex inspections.
- Create an inbound shipment per ASN. Update PO quantities before taking ownership, and close the container on a short ship.
- Estimated landed cost posts at receipt. Clear non-material variances with a journal and material ones with an inventory revaluation.
- Review landed cost templates no more than quarterly, after quarter close.

## Check before go-live
- [ ] Inspection location set as the PO receiving location

## Known failure modes
- Over-shipped containers that cannot be received until the PO is updated

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

5. Return to Debit

Vendor returns and credits, most often for goods damaged on arrival.

Roles: Buyer/Planner, Warehouse Associate, A/P Analyst

Process flow

Mark damaged → Vendor return authorization → Ship back or skip → Vendor credit → Apply or refund

Leading practice rules

  • Mark damaged receipts with an unavailable status and tell the buyer which purchase order they came from.
  • Create vendor returns from the purchase order or bill; attach photos where the vendor needs proof.
  • Where goods need not go back, create the credit from the original bill and write the goods off.
  • Process credits for stocked goods through a vendor return authorization.

Skill file: Return to Debit

---
name: afa-return-to-debit
description: NetSuite leading practice for Return to Debit in apparel, footwear and accessories brands
---

# Return to Debit - Apparel, Footwear and Accessories

## Roles
Buyer/Planner, Warehouse Associate, A/P Analyst

## Process flow
Mark damaged → Vendor return authorization → Ship back or skip → Vendor credit → Apply or refund

## Leading practice rules
- Mark damaged receipts with an unavailable status and tell the buyer which purchase order they came from.
- Create vendor returns from the purchase order or bill; attach photos where the vendor needs proof.
- Where goods need not go back, create the credit from the original bill and write the goods off.
- Process credits for stocked goods through a vendor return authorization.

## Check before go-live
- [ ] Damaged-goods routine shared by warehouse and buying

## Known failure modes
- Damaged goods written off with no vendor credit claimed

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

6. Lead to Quote

Wholesale selling: teams, territories, quotas, opportunities and quotes.

Roles: Sales Representative, Sales & Operations Manager

Process flow

Lead → Territory rule → Opportunity → Quote on the grid → Sales order

Leading practice rules

  • Route leads with territory rules on regions or customer category, not postal codes, which cannot be imported.
  • Create quotes from opportunities, using the grid for bulk entry by style.
  • Opportunities and quotes do not commit or allocate stock, so a prebook is not a reservation until it is a sales order.

Skill file: Lead to Quote

---
name: afa-lead-to-quote
description: NetSuite leading practice for Lead to Quote in apparel, footwear and accessories brands
---

# Lead to Quote - Apparel, Footwear and Accessories

## Roles
Sales Representative, Sales & Operations Manager

## Process flow
Lead → Territory rule → Opportunity → Quote on the grid → Sales order

## Leading practice rules
- Route leads with territory rules on regions or customer category, not postal codes, which cannot be imported.
- Create quotes from opportunities, using the grid for bulk entry by style.
- Opportunities and quotes do not commit or allocate stock, so a prebook is not a reservation until it is a sales order.

## Check before go-live
- [ ] Territories defined by region or category

## Known failure modes
- Prebooks left as quotes, then found to have no stock behind them

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

7. Order Management

Three channels, three ways in: wholesale orders keyed on the grid, web orders by integration, store sales as a nightly summary.

Roles: Sales Representative, Sales & Operations Manager, Customer Service Representative

Process flow

Customer master → Wholesale on the grid / web by integration / store summary nightly → Deposits → Drop ship or special order

Leading practice rules

  • Use parent and child customers for wholesale accounts, and set a default order priority on each customer to steer allocation.
  • Set credit limit handling to warn only.
  • Bring web orders in real time, sync available quantity at least hourly, and keep payment capture in the web platform.
  • Record store sales as a nightly summary cash sale rather than importing full point-of-sale detail.
  • Take preorder deposits as customer deposits and apply them at payment. Keep gift card balances outside the system and the liability inside it.

Skill file: Order Management

---
name: afa-order-management
description: NetSuite leading practice for Order Management in apparel, footwear and accessories brands
---

# Order Management - Apparel, Footwear and Accessories

## Roles
Sales Representative, Sales & Operations Manager, Customer Service Representative

## Process flow
Customer master → Wholesale on the grid / web by integration / store summary nightly → Deposits → Drop ship or special order

## Leading practice rules
- Use parent and child customers for wholesale accounts, and set a default order priority on each customer to steer allocation.
- Set credit limit handling to warn only.
- Bring web orders in real time, sync available quantity at least hourly, and keep payment capture in the web platform.
- Record store sales as a nightly summary cash sale rather than importing full point-of-sale detail.
- Take preorder deposits as customer deposits and apply them at payment. Keep gift card balances outside the system and the liability inside it.

## Check before go-live
- [ ] A customer priority scheme agreed with sales

## Known failure modes
- Web stock synced from on-hand, not available, so the site sells allocated units

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.
Apparel, footwear and accessories process flow: supply from planning and purchasing meets demand from wholesale, web and stores at allocation and commitment

8. Allocation and Commitment

Where the channels compete for the same stock. Supply Allocation commits inventory to order lines by rule, on a schedule or in real time.

Roles: Sales & Operations Manager, Supply Chain Manager, Administrator

Process flow

Define strategy → Set order priority → Schedule by channel → Allocate → Review alerts → Reallocate → Firm

Leading practice rules

  • Keep allocation strategies to as few as possible; one that covers most needs is best.
  • Run at least one allocation schedule per channel. For web orders, stagger hourly schedules no closer than 15 minutes apart to approximate real time.
  • Reallocate through schedules, the Allocate Orders page, or Reallocate Items from allocation alerts. Allocate Orders runs per location, 200 lines at a time.
  • Firming a line protects its allocation but stops it receiving more.
  • Use Advanced Order Management for automatic location assignment, fulfillment requests and store pickup.
  • Recommendation: sort schedules by order priority, then expected ship date.

Skill file: Allocation and Commitment

---
name: afa-allocation-and-commitment
description: NetSuite leading practice for Allocation and Commitment in apparel, footwear and accessories brands
---

# Allocation and Commitment - Apparel, Footwear and Accessories

## Roles
Sales & Operations Manager, Supply Chain Manager, Administrator

## Process flow
Define strategy → Set order priority → Schedule by channel → Allocate → Review alerts → Reallocate → Firm

## Leading practice rules
- Keep allocation strategies to as few as possible; one that covers most needs is best.
- Run at least one allocation schedule per channel. For web orders, stagger hourly schedules no closer than 15 minutes apart to approximate real time.
- Reallocate through schedules, the Allocate Orders page, or Reallocate Items from allocation alerts. Allocate Orders runs per location, 200 lines at a time.
- Firming a line protects its allocation but stops it receiving more.
- Use Advanced Order Management for automatic location assignment, fulfillment requests and store pickup.
- Recommendation: sort schedules by order priority, then expected ship date.

## Check before go-live
- [ ] Saved searches for lines unallocated in the next few days

## Known failure modes
- Each team reallocating for its own channel, so the last change wins unseen

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

9. Fulfillment and Billing

Shipping and invoicing, which also split by channel.

Roles: Warehouse Associate, A/R Analyst, Accounting Manager

Process flow

Bulk fulfill committed orders → Pick → Pack → Ship with labels → Invoice or cash sale → Collect

Leading practice rules

  • Fulfill in bulk when orders are fully committed or ship complete; otherwise fulfill per order.
  • Generate return labels at fulfillment if returns ship free.
  • On split shipments, shipping cost lands on the first fulfillment only; recalculate later ones if charged.
  • Invoice wholesale through billing operations with billing groups by customer category, consolidating for parent accounts.
  • Close a short-paid wholesale invoice with a credit memo to bad debt or a discount item.
  • Where cards are captured in NetSuite at order time, a partly shipped order needs a cash refund for the rest.

Skill file: Fulfillment and Billing

---
name: afa-fulfillment-and-billing
description: NetSuite leading practice for Fulfillment and Billing in apparel, footwear and accessories brands
---

# Fulfillment and Billing - Apparel, Footwear and Accessories

## Roles
Warehouse Associate, A/R Analyst, Accounting Manager

## Process flow
Bulk fulfill committed orders → Pick → Pack → Ship with labels → Invoice or cash sale → Collect

## Leading practice rules
- Fulfill in bulk when orders are fully committed or ship complete; otherwise fulfill per order.
- Generate return labels at fulfillment if returns ship free.
- On split shipments, shipping cost lands on the first fulfillment only; recalculate later ones if charged.
- Invoice wholesale through billing operations with billing groups by customer category, consolidating for parent accounts.
- Close a short-paid wholesale invoice with a credit memo to bad debt or a discount item.
- Where cards are captured in NetSuite at order time, a partly shipped order needs a cash refund for the rest.

## Check before go-live
- [ ] Billing schedules limited to wholesale groups

## Known failure modes
- Billing schedules not limited to wholesale groups, so web orders are invoiced instead of becoming cash sales

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

10. Return to Credit

Customer returns by channel, with exchanges handled as a return plus a new order.

Roles: Customer Service Representative, Sales Representative, Warehouse Associate, Accounting Manager

Process flow

Case → Return authorization with reason → Receive into inspection → Credit memo or cash refund → New order for exchange

Leading practice rules

  • Create the return authorization from the original transaction, link it to the case, and put the return reason on the header.
  • There is no exchange record: credit the return and create a new sales order for the exchange.
  • Receive returns into inspection with Restock checked, then transfer to selling stock or quarantine.
  • Wholesale returns get credit memos and consumer returns get cash refunds, both created from the return authorization.
  • Both debit the sales account by default; posting to Sales Returns and Allowances needs a customization.

Skill file: Return to Credit

---
name: afa-return-to-credit
description: NetSuite leading practice for Return to Credit in apparel, footwear and accessories brands
---

# Return to Credit - Apparel, Footwear and Accessories

## Roles
Customer Service Representative, Sales Representative, Warehouse Associate, Accounting Manager

## Process flow
Case → Return authorization with reason → Receive into inspection → Credit memo or cash refund → New order for exchange

## Leading practice rules
- Create the return authorization from the original transaction, link it to the case, and put the return reason on the header.
- There is no exchange record: credit the return and create a new sales order for the exchange.
- Receive returns into inspection with Restock checked, then transfer to selling stock or quarantine.
- Wholesale returns get credit memos and consumer returns get cash refunds, both created from the return authorization.
- Both debit the sales account by default; posting to Sales Returns and Allowances needs a customization.

## Check before go-live
- [ ] Return reason captured on every authorization

## Known failure modes
- Restock unchecked on receipt, writing returned goods off as a loss

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

11. Marketing and Promotions

Campaigns and promotions, with one decision first: which system owns the promotion engine.

Roles: Sales & Operations Manager, Marketing Manager, Merchandising Manager

Process flow

Decide promotion owner → Target groups → Campaign with costs → Promotions → Markdowns → Analyze

Leading practice rules

  • Where the web platform has its own promotion engine, keep promotions there and record the discount as a discount item with a promo code column.
  • Use SuitePromotions only where promotions are run in NetSuite.
  • Give campaigns a base cost and expected revenue, since costs cannot come from vendor bills.
  • Automate markdowns from the original price with the Effective Date Pricing bundle.

Skill file: Marketing and Promotions

---
name: afa-marketing-and-promotions
description: NetSuite leading practice for Marketing and Promotions in apparel, footwear and accessories brands
---

# Marketing and Promotions - Apparel, Footwear and Accessories

## Roles
Sales & Operations Manager, Marketing Manager, Merchandising Manager

## Process flow
Decide promotion owner → Target groups → Campaign with costs → Promotions → Markdowns → Analyze

## Leading practice rules
- Where the web platform has its own promotion engine, keep promotions there and record the discount as a discount item with a promo code column.
- Use SuitePromotions only where promotions are run in NetSuite.
- Give campaigns a base cost and expected revenue, since costs cannot come from vendor bills.
- Automate markdowns from the original price with the Effective Date Pricing bundle.

## Check before go-live
- [ ] One system named as owner of promotions

## Known failure modes
- Promotions rebuilt in both systems, so order totals disagree

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

12. Customer Service

Cases from web forms, email and phone, routed by rule and linked to the orders and returns they concern.

Roles: Customer Service Manager, Customer Service Representative

Process flow

Capture case → Route by territory → Link to order or return → Escalate on SLA → Resolve

Leading practice rules

  • Capture cases by online form, email capture and phone, routed by case territories built from case rules.
  • Link each case to its sales order or invoice, and to the return authorization once created.
  • Escalate automatically when a case needs an expert or breaches its SLA.

Skill file: Customer Service

---
name: afa-customer-service
description: NetSuite leading practice for Customer Service in apparel, footwear and accessories brands
---

# Customer Service - Apparel, Footwear and Accessories

## Roles
Customer Service Manager, Customer Service Representative

## Process flow
Capture case → Route by territory → Link to order or return → Escalate on SLA → Resolve

## Leading practice rules
- Capture cases by online form, email capture and phone, routed by case territories built from case rules.
- Link each case to its sales order or invoice, and to the return authorization once created.
- Escalate automatically when a case needs an expert or breaches its SLA.

## Check before go-live
- [ ] Email case capture live before go-live

## Known failure modes
- Returns handled outside cases, so return reasons never reach service reporting

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

13. Financial Management

Structure, intercompany and the close, where the choice of intercompany method decides how much work every transfer creates.

Roles: Controller, Accounting Manager, CFO

Process flow

Subsidiaries by tax ID → Chart of accounts and segments → Intercompany method → Amortization and allocations → Close

Leading practice rules

  • Create a subsidiary per tax ID, and an elimination subsidiary before enabling automated eliminations.
  • Use one chart of accounts, with segments rather than child accounts for each cost center.
  • Choose the lightest intercompany method that fits: journals, intercompany transfer orders, or cross-subsidiary fulfillment. Use intercompany purchase and sales orders only when arm's length books are required.
  • Set default deferral accounts on expense accounts to limit amortization templates, and use statistical accounts for dynamic allocations.

Skill file: Financial Management

---
name: afa-financial-management
description: NetSuite leading practice for Financial Management in apparel, footwear and accessories brands
---

# Financial Management - Apparel, Footwear and Accessories

## Roles
Controller, Accounting Manager, CFO

## Process flow
Subsidiaries by tax ID → Chart of accounts and segments → Intercompany method → Amortization and allocations → Close

## Leading practice rules
- Create a subsidiary per tax ID, and an elimination subsidiary before enabling automated eliminations.
- Use one chart of accounts, with segments rather than child accounts for each cost center.
- Choose the lightest intercompany method that fits: journals, intercompany transfer orders, or cross-subsidiary fulfillment. Use intercompany purchase and sales orders only when arm's length books are required.
- Set default deferral accounts on expense accounts to limit amortization templates, and use statistical accounts for dynamic allocations.

## Check before go-live
- [ ] Intercompany method decided per subsidiary pair

## Known failure modes
- Intercompany purchase and sales orders used where a transfer order would do, multiplying transactions

## Scope note
AFA Standard and Premium editions. Confirm against your licensed modules.

Where to Start

Start with the matrix, because choosing Style or Style-Color as the parent decides the product pages, the grid templates and how every SKU is counted, and the costing method set alongside it cannot be changed. Then draw the channel map: which orders are keyed on the grid, which arrive from the web, and which come in as a nightly store summary. Allocation follows and is the hardest design conversation, because it is where wholesale priorities and web promises collide. Procurement, inspection and landed cost come next, with returns, promotions and finance alongside.

Once the system is running, the highest-value habit is a daily look at allocation exceptions: lines that cannot be allocated in the next few days, lines allocated late, and lines firmed by hand. Recommendation: give one person ownership of reallocation across channels, because when each team reallocates for its own channel, the last change wins and nobody sees what it displaced. The season clock, markdown timing and the style-versus-SKU problem are covered in the companion end-to-end guide.

Related Azdan Resources

Published by Azdan, an Oracle NetSuite Solution Provider operating across the UAE, Saudi Arabia, and Egypt. Guidance in this article reflects Azdan's process design work with apparel, footwear and accessories brands. Content checked November 2026.

Hue Hue
Get Started

Ready to Strategize 
Your Next Move?

Let’s talk about your next milestone
Mora Fahmy, Solutions Advisor at Azdan
Mora Fahmy
Solutions Advisor