More users or products
Every current TREX Grow plan includes unlimited users and products, so growth in either number does not create the plan boundary.
TREX Grow Upgrade Readiness
When Should I Upgrade TREX Grow?
Stay on the current plan while it completes the work your team runs today. Test an upgrade when a recurring sales, file, currency, accounting, purchasing, stock or warehouse task needs the next capability, then move only if the tested workflow passes.
Problem
Being busier is not enough reason to upgrade
An upgrade is easiest to defend when it resolves a specific operating constraint. Headcount, catalogue size, a premium label or an untested future scenario do not show that the current plan has reached its limit.
Pricing uncertainty
A headline amount can still leave important conditions unclear.
Billing cycle, country display, plan limits and support policies all affect the decision. Each one should be explicit before payment.
Billing cyclePlan limitsSupport policy
A vague sense of growth
Revenue, workload or team growth may start the review, but the decision still needs a named document, stock control or warehouse step.
One unusual exception
A rare task may be better handled deliberately outside the system until it becomes frequent enough to justify a new operating layer.
A feature that nobody owns
If no responsible person will use and maintain the added workflow, access to the capability will not create operating value.
Premium for reassurance
Premium is for active location-level warehouse control, not a default choice for every growing SME.
Accounting Beta without a reviewer
Accounting Beta is available on paid plans, but it should not drive an upgrade unless the organisation can complete setup, activate it explicitly and have a qualified accountant review important outputs.
Education
The direct answer: upgrade only after five signals line up
A strong upgrade case combines frequency, a plan boundary, ownership, a measurable trial and ongoing use. If one of these is missing, the safer decision is usually to keep the current plan and collect better evidence.
A dated price needs a live final check
Use this page to understand the current conditions, then verify the country-aware amount and checkout wording immediately before payment.
Country + currency
Annual billing
Policy contact
Three checks before paying
1
Verify current price
- - Check country + currency
- - Confirm annual amount
2
Prove workflow fit
- - Start Free or trial
- - Test real work
3
Review conditions
- - Read checkout terms
- - Save support contact
The blocker repeats
The missing step affects a weekly or otherwise recurring workflow, not a hypothetical process or isolated exception.
The capability is named
The team can point to the exact sales, attachment, currency, Accounting Beta, purchasing, stock or warehouse capability outside its current plan.
An owner is responsible
The people who create, review or complete the records will take part in setup and testing.
The trial has a pass condition
The team knows what a successful end-to-end workflow looks like before beginning the 30-day paid-plan trial.
The need will continue
The added operating layer will remain part of normal work after the trial rather than becoming an unused menu.
Solution
Move from Free to Starter when the complete sales workflow becomes recurring
Free can remain the right plan while customers, products, quotations, invoices, Malaysia e-Invoice submission, catalog, RFQ and appointments cover the work. Starter becomes the next layer when the customer cycle needs every supported sales document, file evidence, multi-currency or Accounting Beta without purchasing and inventory management.
A transparent decision connects cost, workflow scope and support terms
Complete sales documents
Test Starter when sales orders, pro-forma invoices, delivery orders, official receipts, returns or supported credit, debit and refund notes become part of the normal customer cycle.
Attachments
Starter supports attachments across the business records it can access when teams repeatedly need images, PDFs or other evidence beside the record.
TREX Grow Pricing
Multi-currency
Customer documents, payment rows and Accounting company expenses that need supported foreign currencies are a Starter-level signal.
Accounting Beta
Starter includes Accounting Beta after setup and explicit activation. Calculations, postings and reports may be incomplete or inaccurate and require qualified review before tax, statutory reporting or important financial decisions.
Solution
Move from Starter to Essential when purchasing or inventory becomes recurring
Starter already covers the complete customer-sales workflow, attachments, multi-currency and Accounting Beta. Essential becomes the next layer when supplier purchasing, stock receipts, corrections or WMS-lite controls become normal operating work.
A transparent decision connects cost, workflow scope and support terms
Purchasing and supplier records
A recurring need for suppliers, purchase orders, supplier invoices, purchase returns or supported supplier notes is an Essential-level signal.
Stock entries and adjustments
Structured replenishment, receipt and correction work requires Essential rather than Starter.
TREX Grow Pricing
Supplier billing and returns
Connected supplier invoices, payments, returns and supported supplier notes belong to the Essential purchasing layer.
WMS-lite handling
Daily stock handling through supported General and BIN locations points to Essential; advanced custom-location controls remain Premium.
Solution
Move from Essential to Premium when warehouse execution needs location depth
Essential already covers broader documents, purchasing, stock records and WMS-lite handling. Premium becomes relevant when the warehouse must control where stock sits, how it moves, what gets picked and how counts are reconciled as part of daily work.
A transparent decision connects cost, workflow scope and support terms
Custom warehouse locations
Use Premium when supported system locations are no longer enough and the team must model its own operating locations.
Location-level movement review
Recurring investigation by location or by product location points to location and product-location ledgers in Premium.
TREX Grow Pricing
Delivery picking
Premium is the relevant test when warehouse staff need a structured delivery-picking flow and picking-list PDF output.
Inventory count sessions
Structured cycle counts or stock takes with expected quantities, entered counts, variance review and approval are Premium-level controls.
Workflow
Run a five-step upgrade readiness check
Treat the upgrade like a small operating decision. Start with a documented blocker, test the exact workflow with representative records and choose the lowest plan layer that removes the constraint without adding unused complexity.
A controlled pricing decision
Check
Open live Pricing for the current country display.
Start
Use Free or begin the right paid-plan trial.
Test
Complete one representative paid workflow.
Confirm
Review the annual amount and checkout terms.
Contact
Email support promptly when a change is needed.
A dependable decision checks the live amount, proves the workflow and keeps the support route visible.
Record one recurring blocked workflow in plain language, including how often it happens and who is affected.
Map the first missing capability to Starter, Essential or Premium using the current Pricing page rather than an old screenshot.
Choose the responsible users and define a pass condition for one representative end-to-end operating cycle.
Use the 30-day paid-plan trial to run that cycle with realistic customers, suppliers, products, documents, locations and quantities.
Upgrade to the smallest plan that passes, or stay on the current plan if the workflow, adoption or evidence remains incomplete.
Upgrade approval evidence
Use the ready and wait signals together. A paid capability is useful only when the team can operate it consistently.
| Evidence | Ready signal | Wait signal |
|---|---|---|
| Frequency | The blocker recurs in normal work | The need is hypothetical or isolated |
| Plan boundary | The missing capability is named and confirmed | The case is based on users, products or a vague growth claim |
| Ownership | Responsible users participate and know the next action | Nobody owns setup, records or review |
| Trial result | A representative cycle meets the agreed pass condition | The team only explores menus or sample screens |
| Ongoing adoption | The added workflow will continue after the trial | The capability is likely to sit unused |
Best practices
Make the upgrade case easy to review
A short evidence pack helps an owner, finance lead and operating team reach the same conclusion. Keep the proof tied to the workflow and current plan boundaries instead of turning the review into a feature-count exercise.
Do this
Use one decision sentence
Write: We should test the next plan because this recurring workflow needs this named capability owned by this team.
Do this
Measure the workflow, not promised ROI
Track whether the cycle can be completed correctly and adopted consistently instead of predicting guaranteed savings or productivity.
Do this
Test with the people who do the work
Include the sales, purchasing, finance or warehouse staff responsible for each hand-off and review point.
Do this
Use current plan information
Verify the latest plan boundary, trial condition and available capability on the live Pricing page before approving the change.
Do this
Keep the decision reversible
Start with the smallest useful scope and trial it before reshaping the team's full operating process around the upgrade.
Verify live Pricing and the final checkout terms before authorising an annual paid plan.
Mistakes
Seven signs you should wait before upgrading
Waiting is a valid decision when the business has not yet proved the need or its readiness. Keep using the current plan, document the workflow and return to the decision when the evidence changes.
Most pricing surprises begin with an unchecked assumption, not the published headline amount.
Common
Core Free workflows still complete the job
If customer, quotation, invoice, e-Invoice, catalog, RFQ and appointment work is enough, Free can remain the right no-expiry plan.
High risk
The trigger is more users or products
Those remain unlimited across current plans and do not justify a higher tier by themselves.
Common
The problem has happened only once
Record the exception and watch for a recurring pattern before adding a permanent operating layer.
High risk
The missing capability is still unclear
A vague request for more control is not enough; identify the document, stock record, warehouse step or review action first.
Common
No one can run the trial
Delay the test until the responsible users can enter representative records, complete the workflow and review the outcome.
High risk
Premium controls will not be used daily
Custom locations, ledgers, picking and counts should match real warehouse execution rather than a distant future plan.
Common
Accounting Beta has no review owner
Wait until someone can complete Accounting setup, acknowledge the Beta status and arrange qualified review of important records and reports before relying on the module.
Next step
Start a 30-Day TrialTest the blocker before you change the plan
Choose one recurring workflow, define what success looks like and use the 30-day paid-plan trial to test the smallest plan layer that could solve it. If the workflow does not pass, keep the current plan and refine the evidence.
Move from Free to Starter when a recurring workflow needs complete sales documents, attachments, multi-currency or Accounting Beta. Move directly to Essential only when purchasing, suppliers, stock entries, adjustments or WMS-lite are also required.