Does buying lead into receiving?
The team should see whether a purchase order can become the source for the stock entry instead of typing the same item and supplier context again.
Back to the product tourInventory Workflow Tour
Tour the TREX Grow inventory workflow from product record to stock review
Tour a real inventory path: start with the product record, receive against a purchase order, capture an adjustment, trace the movement, and see when Premium count controls matter.
Problem
A useful inventory tour must answer operational questions
The decision is not whether the software has an Inventory menu. It is whether purchasing, receiving, stock control and review can complete one shared record chain—and whether your team can explain the resulting quantity without rebuilding the story elsewhere.
Operational pressure
The next action is easy to lose when context is scattered.
When records live in different places, the person responsible has to reconstruct what happened before they can make a confident decision or follow up.
Scattered recordsUnclear ownershipAvoidable surprises
Are quantity states separated?
Available, incoming and reserved quantities should remain distinct so purchasing, sales and fulfilment do not interpret one total differently.
Can exceptions carry a reason?
A correction should show the affected product, quantity, location context, reason, remarks and controlled status used in the workflow.
Can someone reconstruct the change?
The reviewer should be able to trace the product history back to a source record, creator, date and resulting quantity context.
Where does warehouse depth begin?
The tour should distinguish Essential purchasing and core stock work from Premium locations, ledgers, picking and inventory count sessions.
What should the trial prove?
The test needs a pass condition: complete one representative hand-off and explain the final position without a parallel spreadsheet.
Education
The short answer: one product stays connected to the records that move it
TREX Grow starts with a shared product record, then carries that identity into purchasing, PO-linked receiving, inventory adjustments and product movement history. The workflow exposes the context behind the stock position instead of presenting the latest balance as an isolated number.
One product identity
Product name, code, unit of measure, supplier links, reorder settings and approval status provide common context before documents start changing stock.
One source for each movement
Purchase orders, stock entries, deliveries, returns and adjustments give the team a record to inspect when a product quantity changes.
Four facts behind the change
Useful evidence answers which source was used, how much changed, who handled it and when, plus where or why when the workflow requires that context.
Three quantity states
Available, incoming and reserved stock remain visible as different operating signals instead of being compressed into a single ambiguous total.
Workflow
Run this six-stop inventory workflow during the trial
Use one current SKU and one realistic receipt so every stop produces evidence for the next. The final test is simple: another responsible user can explain the product position from TREX Grow without asking you to rebuild it in a spreadsheet.
A repeatable operating workflow
Capture
Record the current facts in one shared place.
Check
Confirm what is known and what needs attention.
Assign
Make the next decision or follow-up accountable.
Act
Complete the next task and record the outcome.
Review
Refresh the shared view when facts change.
A dependable workflow keeps the shared record and the next action aligned.
Pick one real product and confirm its code, unit of measure, supplier context, reorder settings and current available, incoming and reserved quantities.
Create a purchase order for that product using the supplier and expected quantity your team would use in normal work.
Start the stock entry from the purchase order, record the quantity actually received and check how shortage or oversupply is shown.
Create one representative inventory adjustment with a quantity, reason and remarks, then review the status and decision evidence your process requires.
Open the product history and ask a second user to find the movement source, changed quantity, creator, date and resulting stock context.
If warehouse depth is required, use Premium to scope an inventory count session by count type, location and product, then confirm who owns the variance review.
What to observe at each tour stop
Use the screen and question together; clicking the menu alone does not prove the hand-off works for your team.
| Tour stop | Screen evidence | Decision question |
|---|---|---|
| 1. Product record | Code, UOM, supplier context, reorder settings and three quantity states | Can every team identify the same item and interpret its current position? |
| 2. Purchase order | Supplier, product and expected quantity | Does the buying record contain enough context for receiving? |
| 3. Stock entry | PO source, received quantity, reference, dates and shortage or oversupply | Can the receiver record what arrived without re-keying the purchase story? |
| 4. Adjustment | Product, location, quantity, reason, remarks, creator and status | Can the team explain and review an exception? |
| 5. Product history | Source record, changed quantity, creator and date | Can another user reconstruct why the balance changed? |
| 6. Inventory count | Count type plus optional location and product scope | Does the warehouse need Premium count controls or only core stock records? |
Education
Stop 1: read the product record before changing stock
The product list is the shared starting point. This real TREX Grow screen uses safe demo records and exposes the item identity, available, incoming and reserved quantities, unit of measure, reorder point, reorder quantity and approval status before the team creates the next movement.
Confirm the item identity
Use the product name and product code to make sure purchasing, warehouse and sales staff are discussing the same record.
Read all three quantity states
Available, incoming and reserved quantities answer different operating questions and should not be treated as interchangeable.
Use reorder settings as attention context
The reorder point and reorder quantity help the team decide what needs review; they do not by themselves prove an automatic replenishment workflow.
Check the controlled status
Approval or finalised status gives responsible users a visible checkpoint before the product drives downstream work.
Best practices
Stop 2: receive from the purchase order, not from a blank total
The stock entry screen preserves the purchasing source and then asks the receiver to record what actually arrived. That creates a cleaner hand-off than copying an ordered quantity into a separate stock spreadsheet with no link back to the supplier record.
Do this
Start from the source record
Use the relevant purchase order so the supplier, product and expected delivery quantity enter the receiving step with context.
Do this
Record the actual receipt
Enter the quantity received rather than assuming the ordered quantity and the delivered quantity are always identical.
Do this
Make the variance visible
Review the matched, shortage or oversupply state so the team can decide whether a follow-up is required.
Do this
Keep the reference and evidence
Use the stock-entry reference, received and checked dates, allocation context and supported attachment area according to your receiving procedure.
The best practice is to make the next action clear before the situation becomes urgent.
Education
Stop 3: record an inventory exception with review evidence
A controlled adjustment should explain more than the new total. This real approved TREX Grow record shows the affected product, location, adjusted quantity, correction reason, remarks, creator, creation time, approver and approval time in the same review context.
Name the affected product
Keep the adjustment tied to the same product record the team uses for purchasing, receiving and movement review.
State the quantity and reason
Record what changed and why, using a reason that another responsible user can understand later.
Add remarks for the exception
Use concise remarks to capture the operating context that a generic correction label would otherwise lose.
Review ownership and status
Check the creator, date, approval state, approver and decision time where the configured workflow uses those controls.
Best practices
Stop 4: trace the movement from the product history
The product view brings movement context back to the item. The history screen shows current quantity states and a linked movement record alongside the product code, SKU, barcode field, unit, status and reorder settings, giving the reviewer one place to begin the explanation.
Do this
Start with the current position
Read the available, incoming and reserved quantities before investigating the event that changed the product.
Do this
Open the source movement
Use the linked stock entry, adjustment, delivery or return record instead of treating the history line as the whole explanation.
Do this
Verify ownership and time
Check who created the event and when it occurred so the follow-up reaches the responsible person with the right context.
Do this
Explain the balance aloud
Ask a second user to reconstruct the story from the product screen; gaps in the explanation reveal where the process or permissions need refinement.
The best practice is to make the next action clear before the situation becomes urgent.
Education
Stop 5: add inventory counts only when warehouse depth is required
Premium adds structured inventory count sessions for teams that need cycle-count or stock-take scope by location and product. This is a warehouse-control boundary, not a reason to skip the core product, purchasing, receiving and adjustment workflow the team must prove first.
Choose the count purpose
Select a cycle count for a bounded review or a stock take for a broader counting exercise according to your operating procedure.
Scope by location
Use location filters when the count should focus on selected warehouse areas rather than all pickable stock.
Scope by product
Use product filters when the team needs to review one SKU group, a high-risk category or a fast-moving item.
Define the variance decision
Before rollout, document who reviews count differences and which supported adjustment or follow-up record should resolve them.
Inventory tour scope by TREX Grow plan
Use the current Pricing page as the final source for plan availability because entitlements can change.
| Plan | Inventory tour scope | Use it when |
|---|---|---|
| Free | Core product records with unlimited users and products | You want to prepare shared product data before testing paid inventory workflows. |
| Starter | Complete sales documents, attachments and multi-currency; no inventory management | Your operation needs deeper sales work but not purchasing or inventory controls. |
| Essential | Purchase orders, stock entries, inventory adjustments, returns, supplier records and WMS-lite handling | Purchasing and core stock movements need to stay connected. |
| Premium | Essential plus custom locations, location and product-location ledgers, picking, picking-list PDFs and inventory count sessions | Warehouse location, fulfilment and formal counting controls are daily work. |
Best practices
Use the tour as a rollout gate, not a product demo
A polished screen is not implementation proof. Before choosing a plan, test one normal receipt and one realistic exception with the people who will own purchasing, receiving, stock review and approval, then document every capability that still needs separate verification.
Do this
Use representative records
Choose a real product shape, supplier relationship, quantity and receiving scenario without exposing confidential live data in the trial.
Do this
Include each workflow owner
Let purchasing, receiving, inventory control and the responsible reviewer complete the step they will own after rollout.
Do this
Test normal work and one exception
A clean receipt proves the happy path; a shortage, oversupply or correction reveals whether ownership and evidence stay clear when work deviates.
Do this
Confirm permissions and approval rules
Review which users can create, edit, approve and inspect the relevant records for your organisation before relying on the configured path.
Do this
Separate specialist requirements
Verify manufacturing, serial, batch, expiry, scanner-led receiving, label printing, forecasting, integrations and costing needs independently instead of assuming they are included.
Do this
Review security before rollout
Use the TREX Grow Data Security page and your own access review to assess account controls, public-link handling and operational responsibilities.
The best practice is to make the next action clear before the situation becomes urgent.
Next step
Start the 30-Day TrialProve the inventory workflow with one real scenario
Use the 30-day paid-plan trial to test a product, purchase order, stock entry, adjustment and movement review from start to finish. Add Premium count controls only if locations, picking, ledgers or formal counts are part of the workflow your team must run.
An inventory workflow tour shows how the actual product screens connect across one operating scenario. This TREX Grow tour follows a product record into purchase-order-linked receiving, quantity review, an inventory adjustment, movement history and an optional Premium inventory count.