A retailer runs the same process areas whether it has one store or two hundred. What changes with scale is not the processes but how many of the decisions inside them were made deliberately, and several of the most consequential ones look like settings rather than decisions. This is the leading practice reference for retail: 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 retail 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 Retail Standard edition 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 8 Process Areas
Master Data Management → Item Management → Procure to Pay → Order to Cash → Marketing to ROI → Return to Credit → Return to Debit → Financial Management
Process area
Primary owner
What it covers
Master Data Management
Accountant
Subsidiaries, segments, locations, customers, vendors and contacts.
Item Management
Inventory Manager
Items, variants, costing and where stock physically sits.
Procure to Pay
Purchasing Manager
Purchasing and vendor management, from deciding what to buy through to paying for it.
Order to Cash
Sales
Order management, fulfillment, payment and the movement of stock between stores.
Marketing to ROI
Sales Manager
Promotions, target groups and upsell.
Return to Credit
Customer Service
Customer returns, credits and refunds.
Return to Debit
Inventory Manager
Vendor returns, credits and refunds.
Financial Management
Accountant
Accounts, journals, reconciliation, period close and reporting.
One further area, Call to Resolution, appears in the edition without documented process content. It is listed here for completeness and not covered below.
1. Master Data Management
Subsidiaries, segments, locations, customers, vendors and contacts. In retail the location structure is the part that matters most, because every store is an inventory location and the reporting only works if the segments hang together.
Define subsidiaries → Set up segments → Create store and warehouse locations → Load customers, vendors and contacts → Validate
Leading practice rules
Subsidiaries are the primary classification for organizing records. Departments, classes and locations can be used alongside them, but each must be associated with a subsidiary before it can be selected on a record or transaction.
Use locations to track physical inventory and employee locations.
Use contact records to hold details for individuals, attachable to a lead, prospect, customer, vendor or partner.
Track vendor addresses for their locations and offices on the vendor record.
Skill file: Master Data Management
---
name: retail-master-data-management
description: NetSuite leading practice for Master Data Management in retail
---
# Master Data Management - Retail
## Roles
Accountant, Inventory Manager, Warehouse Manager, Sales
## Process flow
Define subsidiaries → Set up segments → Create store and warehouse locations → Load customers, vendors and contacts → Validate
## Leading practice rules
- Subsidiaries are the primary classification for organizing records. Departments, classes and locations can be used alongside them, but each must be associated with a subsidiary before it can be selected on a record or transaction.
- Use locations to track physical inventory and employee locations.
- Use contact records to hold details for individuals, attachable to a lead, prospect, customer, vendor or partner.
- Track vendor addresses for their locations and offices on the vendor record.
## Check before go-live
- [ ] Every department, class and location associated with the correct subsidiary
- [ ] Location structure agreed for stores, warehouses and any fulfillment partners before go-live
## Known failure modes
- Segments created without subsidiary associations, so they cannot be selected where they are needed
## Scope note
This reflects the Retail Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
2. Item Management
Items, variants, costing and where stock physically sits. Two decisions here govern everything downstream: how variants are structured, and which average costing method runs across stores.
Define item types → Build matrix styles → Choose group or kit → Set costing method → Assign to locations → Count
Leading practice rules
Use matrix items where a parent item, often called a style, is sold in options such as color and size. The parent SKU links to child SKUs representing every purchasable combination, and the children roll up to the parent.
Use item groups to add several items to an order without adding each one. A group's price is the aggregate of its items and cannot be set separately.
Use kit items where a multi-component item is fulfilled without assembly. A kit's price can be set independently and it carries its own GL account, while cost of goods sold still derives from the components. Kits cannot be added to purchase orders.
Use discount item records to apply line-level discounts.
Standard average cost is location specific. Group Average Cost lets an item carry the same average cost across multiple locations, which is what keeps store margins comparable.
Stores need the same inventory capability as a warehouse, so maintain each physical store as its own inventory location.
Develop a cycle count strategy that classifies items by movement velocity and sets how often each class is counted. Inventory counts take a snapshot of on-hand stock for the items selected.
Where stock is held by Amazon FBA, cycle counts and physical year end are performed outside NetSuite, because FBA is the inventory system of record.
Skill file: Item Management
---
name: retail-item-management
description: NetSuite leading practice for Item Management in retail
---
# Item Management - Retail
## Roles
Inventory Manager, Accountant, Purchasing Manager, Warehouse Manager
## Process flow
Define item types → Build matrix styles → Choose group or kit → Set costing method → Assign to locations → Count
## Leading practice rules
- Use matrix items where a parent item, often called a style, is sold in options such as color and size. The parent SKU links to child SKUs representing every purchasable combination, and the children roll up to the parent.
- Use item groups to add several items to an order without adding each one. A group's price is the aggregate of its items and cannot be set separately.
- Use kit items where a multi-component item is fulfilled without assembly. A kit's price can be set independently and it carries its own GL account, while cost of goods sold still derives from the components. Kits cannot be added to purchase orders.
- Use discount item records to apply line-level discounts.
- Standard average cost is location specific. Group Average Cost lets an item carry the same average cost across multiple locations, which is what keeps store margins comparable.
- Stores need the same inventory capability as a warehouse, so maintain each physical store as its own inventory location.
- Develop a cycle count strategy that classifies items by movement velocity and sets how often each class is counted. Inventory counts take a snapshot of on-hand stock for the items selected.
- Where stock is held by Amazon FBA, cycle counts and physical year end are performed outside NetSuite, because FBA is the inventory system of record.
## Check before go-live
- [ ] Costing method decided before the first receipt, with the store margin consequence understood
- [ ] Matrix options agreed for every style range before the item load
- [ ] Cycle count classes and frequencies defined per location
## Known failure modes
- Location-specific average cost left in place across a store estate, so identical items carry different costs and store margins cannot be compared
- Counting FBA inventory in NetSuite as if it were the system of record
## Scope note
This reflects the Retail Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
3. Procure to Pay
Purchasing and vendor management, from deciding what to buy through to paying for it. In a multi-store business the first question is not what to order but whether it needs ordering at all.
Determine items to order → Check other locations → Raise purchase order → Approve → Receive with estimated landed cost → Approve bill → Pay
Leading practice rules
Use the Order Items page to find items running low, and check whether another location can replenish before raising a purchase order.
Perform reorder point planning before ordering, to set supply against anticipated demand.
A purchase order is auto-approved within the requestor's purchase limit. Above it, the requestor's supervisor or the next role in the chain with sufficient limit approves.
Apply estimated landed cost at receipt, using cost categories such as freight, duty and insurance with the correct GL accounts and item defaults, so inventory is valued properly from the moment it lands.
For drop ship and special order items, set cost estimate type to Purchase Order Rate. Landed cost cannot be applied to drop ship purchase orders, because the goods are never received into a location.
Use a role-based vendor bill approval with separation of duties, so a bill without a purchase order cannot post until it has been reviewed.
Use in-transit vendor payments to show funds that have left but not yet cleared, for better visibility in the general ledger.
Skill file: Procure to Pay
---
name: retail-procure-to-pay
description: NetSuite leading practice for Procure to Pay in retail
---
# Procure to Pay - Retail
## Roles
Purchasing Manager, A/P Analyst, Accountant, Inventory Manager
## Process flow
Determine items to order → Check other locations → Raise purchase order → Approve → Receive with estimated landed cost → Approve bill → Pay
## Leading practice rules
- Use the Order Items page to find items running low, and check whether another location can replenish before raising a purchase order.
- Perform reorder point planning before ordering, to set supply against anticipated demand.
- A purchase order is auto-approved within the requestor's purchase limit. Above it, the requestor's supervisor or the next role in the chain with sufficient limit approves.
- Apply estimated landed cost at receipt, using cost categories such as freight, duty and insurance with the correct GL accounts and item defaults, so inventory is valued properly from the moment it lands.
- For drop ship and special order items, set cost estimate type to Purchase Order Rate. Landed cost cannot be applied to drop ship purchase orders, because the goods are never received into a location.
- Use a role-based vendor bill approval with separation of duties, so a bill without a purchase order cannot post until it has been reviewed.
- Use in-transit vendor payments to show funds that have left but not yet cleared, for better visibility in the general ledger.
## Check before go-live
- [ ] Purchase limits set per role and approval chain tested
- [ ] Estimated landed cost defaults assigned per item category
## Known failure modes
- Buying stock that another store already holds, because the transfer option was never checked
- Vendor bills without a purchase order posting unreviewed
## Scope note
This reflects the Retail Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
4. Order to Cash
Order management, fulfillment, payment and the movement of stock between stores. Several controls here sit before fulfillment rather than after it, which is where they are cheapest.
Define order strategy → Create sales order → Validate and approve → Fulfill or transfer → Invoice → Collect payment
Leading practice rules
Define the order management and returns strategy, and the reporting it needs, before configuring the flow.
Validate orders against the customer's business rules before they proceed to fulfillment.
Sales orders requiring approval cannot be fulfilled or invoiced until approved.
Drop ship purchase orders are created from the sales order and go vendor direct to customer without touching inventory.
Transfer orders move stock between stores and warehouses. The source location is alerted that the order is pending fulfillment, packs and ships it, and the destination puts it away and marks it received.
Invoices are delivered by the customer's preferred method, including email, print or EDI. Populate the invoice email field on the customer record.
Apply customer payments to open invoices on the customer payment page.
Skill file: Order to Cash
---
name: retail-order-to-cash
description: NetSuite leading practice for Order to Cash in retail
---
# Order to Cash - Retail
## Roles
Sales, Sales Manager, Warehouse Manager, Warehouse Operator, A/R Analyst
## Process flow
Define order strategy → Create sales order → Validate and approve → Fulfill or transfer → Invoice → Collect payment
## Leading practice rules
- Define the order management and returns strategy, and the reporting it needs, before configuring the flow.
- Validate orders against the customer's business rules before they proceed to fulfillment.
- Sales orders requiring approval cannot be fulfilled or invoiced until approved.
- Drop ship purchase orders are created from the sales order and go vendor direct to customer without touching inventory.
- Transfer orders move stock between stores and warehouses. The source location is alerted that the order is pending fulfillment, packs and ships it, and the destination puts it away and marks it received.
- Invoices are delivered by the customer's preferred method, including email, print or EDI. Populate the invoice email field on the customer record.
- Apply customer payments to open invoices on the customer payment page.
## Check before go-live
- [ ] Order validation rules written down before configuration, not discovered during testing
- [ ] Transfer order alerts reaching the right person at each source location
## Known failure modes
- Transfer orders left unreceived at the destination, so stock sits in transit in the system while it is already on the shelf
## Scope note
This reflects the Retail Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
5. Marketing to ROI
Promotions, target groups and upsell. Lightly documented in the edition, and worth keeping close to the item and pricing structure it depends on.
Roles: Sales Manager, Sales
Process flow
Define target groups → Set up promotions → Configure upsell criteria → Run → Measure
Leading practice rules
Set up target groups so a campaign reaches the right audience and marketing traffic stays proportionate.
Use the Standard Promotions feature to assign a promotional discount to one or more items.
Use Upsell Manager to define upsell opportunities, recommendations and criteria for targeted customer groups.
Skill file: Marketing to ROI
---
name: retail-marketing-to-roi
description: NetSuite leading practice for Marketing to ROI in retail
---
# Marketing to ROI - Retail
## Roles
Sales Manager, Sales
## Process flow
Define target groups → Set up promotions → Configure upsell criteria → Run → Measure
## Leading practice rules
- Set up target groups so a campaign reaches the right audience and marketing traffic stays proportionate.
- Use the Standard Promotions feature to assign a promotional discount to one or more items.
- Use Upsell Manager to define upsell opportunities, recommendations and criteria for targeted customer groups.
## Check before go-live
- [ ] Promotions tied to identifiable items so their effect can be measured afterwards
## Known failure modes
- Promotions run without a way to attribute the sales they produced, so they are repeated whether they worked or not
## Scope note
This reflects the Retail Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
6. Return to Credit
Customer returns, credits and refunds. In an omnichannel retailer the refund does not always happen in the ERP at all, and that division has to be designed rather than discovered.
Create return authorization → Approve → Receive returned items → Create credit memo → Apply credit or refund
Leading practice rules
Start every customer return with a return authorization.
Monitor dashboard reminders for return authorizations awaiting approval.
Create item receipts for returned goods against the open return authorization.
Generate credit memos from the return authorization, then apply open credits to open invoices. With no open invoices, hold the credit on the customer record.
Where payment was taken in NetSuite, return authorizations sit in Pending Refund status and are processed from the Refund Return Authorizations page.
Where the customer bought online, the refund is executed in the ecommerce platform, not in NetSuite. The credit memo or refund, depending on the partner integration in use, triggers it.
Skill file: Return to Credit
---
name: retail-return-to-credit
description: NetSuite leading practice for Return to Credit in retail
---
# Return to Credit - Retail
## Roles
Customer Service, Sales Manager, Inventory Manager, Warehouse Operator, A/R Analyst
## Process flow
Create return authorization → Approve → Receive returned items → Create credit memo → Apply credit or refund
## Leading practice rules
- Start every customer return with a return authorization.
- Monitor dashboard reminders for return authorizations awaiting approval.
- Create item receipts for returned goods against the open return authorization.
- Generate credit memos from the return authorization, then apply open credits to open invoices. With no open invoices, hold the credit on the customer record.
- Where payment was taken in NetSuite, return authorizations sit in Pending Refund status and are processed from the Refund Return Authorizations page.
- Where the customer bought online, the refund is executed in the ecommerce platform, not in NetSuite. The credit memo or refund, depending on the partner integration in use, triggers it.
## Check before go-live
- [ ] The boundary between NetSuite refunds and ecommerce refunds agreed and documented per channel
- [ ] Returns performance tracked, so recurring causes surface
## Known failure modes
- Refunding an online order in both systems, or in neither, because nobody decided which one owns the refund
## Scope note
This reflects the Retail Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
7. Return to Debit
Vendor returns, credits and refunds. The retail detail here is that vendor credits arise from more than returns: late deliveries, damaged goods and contract breaches all produce them.
Create vendor return authorizations from the originating purchase transaction for unwanted or damaged items.
Approve or reject vendor return authorizations according to policy, prompted by dashboard alerts or email.
Monitor vendor return authorizations on dashboards and generate the return item fulfillments to send goods back.
Raise vendor credits where contract terms are breached, such as late deliveries or damaged items, as well as for returns and negotiated discounts.
Apply vendor credits to reduce accounts payable.
Track vendor return performance through dashboard alerts, KPIs, vendor scorecards and searches.
Skill file: Return to Debit
---
name: retail-return-to-debit
description: NetSuite leading practice for Return to Debit in retail
---
# Return to Debit - Retail
## Roles
Inventory Manager, Purchasing Manager, Warehouse Manager, Accountant, A/P Analyst
## Process flow
Vendor return authorization → Approve → Return item fulfillment → Vendor credit → Apply → Monitor
## Leading practice rules
- Create vendor return authorizations from the originating purchase transaction for unwanted or damaged items.
- Approve or reject vendor return authorizations according to policy, prompted by dashboard alerts or email.
- Monitor vendor return authorizations on dashboards and generate the return item fulfillments to send goods back.
- Raise vendor credits where contract terms are breached, such as late deliveries or damaged items, as well as for returns and negotiated discounts.
- Apply vendor credits to reduce accounts payable.
- Track vendor return performance through dashboard alerts, KPIs, vendor scorecards and searches.
## Check before go-live
- [ ] Vendor scorecard defined, so repeat offenders are visible
## Known failure modes
- Late or damaged deliveries absorbed without a vendor credit, because only physical returns were being tracked
## Scope note
This reflects the Retail Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
8. Financial Management
Accounts, journals, reconciliation, period close and reporting. Retail adds one structural decision that no other vertical in this series needs: the calendar itself.
Set the retail calendar → Maintain accounts → Post and approve journals → Reconcile → Close → Report
Leading practice rules
Use the 4-5-4 calendar, which divides the year into months of four, five and four weeks. It lines up holidays and gives comparable months the same number of Saturdays and Sundays, so like days are compared to like days.
Consolidate accounts as much as possible and use segmentation for reporting dimensions, with a logical numbering convention by account type.
Use parent and child accounts for summary reporting with drill-down. Two levels are recommended, three at most.
Avoid adjustment periods where possible, because they take additional time to manage.
Journal entries are approved by the creator's supervisor before posting. A different posting period can be chosen at approval, but not a closed one.
Use memorized journals with dashboard reminders for recurring allocations and accruals, and reversing journals where an entry must reverse itself.
Use the automated period and year end feature, which closes the year, calculates and posts retained earnings, and calculates the CTA.
Skill file: Financial Management
---
name: retail-financial-management
description: NetSuite leading practice for Financial Management in retail
---
# Financial Management - Retail
## Roles
Accountant, Controller, Executive, A/R Analyst, A/P Analyst
## Process flow
Set the retail calendar → Maintain accounts → Post and approve journals → Reconcile → Close → Report
## Leading practice rules
- Use the 4-5-4 calendar, which divides the year into months of four, five and four weeks. It lines up holidays and gives comparable months the same number of Saturdays and Sundays, so like days are compared to like days.
- Consolidate accounts as much as possible and use segmentation for reporting dimensions, with a logical numbering convention by account type.
- Use parent and child accounts for summary reporting with drill-down. Two levels are recommended, three at most.
- Avoid adjustment periods where possible, because they take additional time to manage.
- Journal entries are approved by the creator's supervisor before posting. A different posting period can be chosen at approval, but not a closed one.
- Use memorized journals with dashboard reminders for recurring allocations and accruals, and reversing journals where an entry must reverse itself.
- Use the automated period and year end feature, which closes the year, calculates and posts retained earnings, and calculates the CTA.
## Check before go-live
- [ ] Retail calendar settled before the chart of accounts is built
- [ ] Account hierarchy kept to two levels unless there is a reason for a third
## Known failure modes
- Adopting 4-5-4 after a year of calendar-month history, so every comparative has to be rebuilt
## Scope note
This reflects the Retail Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
Where to Start
Master data first, including the location structure, because every store is an inventory location and segments have to be associated with a subsidiary before they can be used. Then item management, where the costing method and the matrix structure are decided. Procure to pay and order to cash next, then the two return processes and marketing. Financial management runs throughout, and the retail calendar has to be settled before any of it produces comparatives.
The single highest-value check across all of them: confirm which average costing method is in use. Standard average cost is location specific, so the same item carries a different cost in every store and store margins stop being comparable. Group Average Cost keeps one cost across locations, and it is a decision to make before the first receipt, not after a year of history.
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 retail businesses. Content checked August 2026.
Blog
News & Insights
Fresh thinking and real-world advice to help you scale smarter, faster, and with more clarity
.svg)
.png)
