AWRA OpsHub Search
Intermediate Certificate on pass

Item Master Governance

Control item changes, approval requests, SKU rules, lifecycle state, and audit trails.

4 lessons 56 min 7-question assessment 70% to pass

What you’ll learn

  • Set rules for creating and changing item records
  • Use SKUs and naming standards to protect reporting
  • Route sensitive item changes through approval
  • Review item audit trails after major changes

Course content

4 lessons · 56 min of reading
01
Lesson 1 of 4 Reading 12 min

Govern the item record

Item Master Governance focuses on keeping item identity, SKU rules, approval requests, and item change history controlled. In AWRA, that work affects item setup, stock movement quality, reporting trust, and the decisions managers make from inventory data.

The important habit is to treat inventory records as operational evidence. Names, quantities, costs, statuses, attachments, labels, and timelines all shape what users can safely sell, move, count, or report.

In practice, an admin changes a taxable item category only after checking SKU rules, report impact, and whether approval is needed. The flow below shows the record sequence a team should understand before changing item data or acting on a stock signal.

Item governance flow

1

Request

User asks to create or change an item.

2

Validate

Check name, SKU, unit, category, tax, and duplicates.

3

Approve

Route sensitive changes for manager review.

4

Apply

Update the item with notes and clear owner.

5

Review

Audit changes and report impact.

Inventory model

  • Item records are shared across modules.
  • SKU rules protect unique identification.
  • Approvals reduce risky item changes.
  • Audit history explains what changed.
02
Lesson 2 of 4 Workshop 15 min

Approve sensitive changes

A reliable inventory routine has a clear trigger, owner, check, and result. The routine for this course is validate item identity, check duplicates and reporting impact, approve sensitive changes, and document the change.

Users should pause before making changes that affect availability, cost, traceability, or reporting. The right pause checks SKU uniqueness, naming, category, tax behavior, unit, duplicates, cost impact, and approval requirement.

In practice, a buyer requests a new item, but inventory verifies it is not already listed under a different name before approving creation. Use the table below to choose the next action from the signal in front of you.

Item change guide

Signal Check Action
New item request Duplicate and SKU rules Create only after validation
Category change Reports and tax behavior Approve before applying
Unit change Stock and purchase impact Review movement history
Item retirement Open stock and transactions Disable rather than delete history

Operator decisions

  • Item changes affect stock, sales, procurement, and reports.
  • Duplicates are easier to prevent than repair.
  • Sensitive changes need approval context.
  • Retirement preserves history better than blind deletion.
03
Lesson 3 of 4 Practice 15 min

Review item history

Inventory work becomes trustworthy when it leaves proof. Strong evidence includes approval notes, item audit events, duplicate checks, SKU decisions, and change requests, connected to the item or movement that changed operational truth.

Review is where teams catch patterns. A one-time correction may close the immediate issue, while repeated exceptions can reveal training, setup, supplier, branch, or process problems.

In practice, the item owner confirms the updated item can be used in transactions and reports without confusing history. The checklist below is the final guardrail before a user treats the record as ready for reporting or action.

Item governance checklist

SKU and name are unique
Category and tax behavior are correct
Sensitive change was approved
Open transactions were considered
Audit notes explain the change

Proof and review

  • Item governance protects every downstream transaction.
  • A clean item record is a reporting asset.
  • Audit review makes changes defensible.
  • Closure means the item is safe to use.
04
Lesson 4 of 4 Reading 14 min

Retiring records instead of deleting them

A record you have finished with, such as an item you no longer stock, a supplier you stopped buying from or a warehouse that closed, is made inactive rather than deleted. On an item, open it and use Make inactive, or set Status to Inactive on its Edit form; most other records take a Status field on their Edit form. An inactive record leaves the pickers where new work starts: item search and the till, the supplier list on an RFQ, the warehouse and bin fields on a check-in, the account list on a journal. Anything new that names it is refused with its name, on the web, through the API, in the mobile app and when the app’s offline queue replays later, so a stale screen or a phone that was out of signal cannot slip one through. Records that already carry it keep it and can still be edited and saved, and every past movement, document and report still shows it. Delete is only for a record created by mistake that never moved.

AWRA will not retire a record that still holds something, because that something would be stranded where nobody can reach it, and the refusal lists what is left. An item is refused while it has stock on hand or an open hold; a supplier while a purchase order is open or a contract is in force; a customer while invoices are unpaid, a sales order is open, a recurring schedule runs or stock is held for them; a warehouse or bin while it holds stock or assets, has open transfers, counts or orders, or has POS counters or users assigned to it; a ledger account while it has a balance or a draft will post to it; a department while it has open requisitions or current staff; a till while its cash drawer is open; a leave type while a request of that type is pending. Defaults cannot be retired at all: the default warehouse, a warehouse’s default bin, system ledger accounts, the General category, the default departments and the two default adjustment reasons. A user named on an approval rule step cannot be deactivated until someone else, or a role, is named on that step instead.

A few records use their own words for the same idea. A customer is Active, Prospect, Suspended or Inactive: Active and Prospect can be sold to, Suspended is a temporary hold such as while an account is overdue, and Inactive means you no longer trade with them, while payments and credit notes still go through for both. A count plan is Active, Paused or Archived, a bank account is closed and reopened from the bank page, and a till is Closed. The lists for items, suppliers, customers, warehouses, bins, ledger accounts and count plans each have a Status filter, so set it to Inactive to find a retired record again; a retired record can be made active at any time. In practice: a hardware shop in Nakuru stops carrying one paint brand. The buyer tries to make the item inactive and is told 14 tins are still on hand, so the branch sells them down first and then retires the item; last year’s sales report still lists it. Once the final purchase order from that brand’s supplier is received, the supplier is made inactive too, and its last bill is still paid in full, because bills and payments are never refused for an inactive supplier.

Before you retire a record

Record Refused while it has Clear it by
Item Stock on hand or an open hold Sell, issue, transfer or count it out
Supplier An open purchase order or a contract in force Receive or close the order; let the contract end
Customer Unpaid invoices, an open sales order, a recurring schedule or a stock hold Collect, close or release them, or use Suspended
Warehouse or bin Stock, assets, open transfers, counts or orders, POS counters or users Move them out or reassign them
Ledger account A balance, or a draft that will post to it Post or clear to zero first
Department Open requisitions or current staff Close the requisitions and move the staff
Till An open cash drawer Count and close the drawer

Retire, do not delete

  • An inactive record leaves the pickers for new work and is refused on the web, the API, the mobile app and the offline queue.
  • Records already carrying it keep it and still save, and history and reports keep showing it; delete is only for a mistake that never moved.
  • Retiring is refused while the record still holds stock, a balance, open orders, unpaid invoices, pending requests, current staff or an open drawer, and default records can never be retired.
  • The Status filter on the list finds a retired record again, and it can be made active at any time.

Finished the material?

Take the 7-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center