Your business has grown. Has the way it works kept up?
Growth often moves faster than the systems behind it. Connect what you have, fix what slows you down, and only replace what is worth it.
Step 2 of 3
What does your business do?
Does this sound familiar?
- Opening a branch means recreating products, prices, permissions and reporting.
- Sales promises depend on calls to the warehouse or factory.
- Finance discovers margin problems after the month has closed.
- Key employees manually connect systems and become operational bottlenecks.
- Online growth creates more administration instead of more capacity.
- A second company or country means intercompany invoices and a consolidation spreadsheet.
- Sales in more than one currency, and local tax in each country, are handled outside the system.
- Group figures are put together by hand at every month end.
Journeys we would explore with you
Each journey shows who does what, the information that follows the work, and how decisions improve. Existing systems you want to keep stay in place.
Does the new operation need a warehouse, branch or separate legal company?
Branch needs a product the group does not stock. A request goes to the catalog owner, so the product is added once and stays consistent across branches.
The objective. Operations wants a new branch trading on the group's catalog, prices and controls from day one, with local staff seeing only what they need.
How the work flows
- Operations director Defines the branch as a branch of the company or a new warehouse, depending on legal and tax needs. Decision: Does the new operation need a warehouse, branch or separate legal company?
- Commercial manager Assigns the shared catalog and the regional price list, adding local prices only where agreed.
- IT or system owner Grants branch staff access through standard roles rather than individual setups.
- Branch manager Sets reordering rules for the branch's stock based on expected demand.
- Branch staff Trade from the first day using the same order, delivery and invoice process as other branches.
- Finance Reports branch results alongside existing branches using analytic accounts or branch reporting.
What must stay connected
- Shared product catalog
- Group and regional price lists
- Access by role
- Branch stock and reordering
- Branch-level financial reporting
When it doesn't go to plan
Branch needs a product the group does not stock
A request goes to the catalog owner, so the product is added once and stays consistent across branches.
Existing payroll or HR system is retained
Branch staff are maintained in the retained system and only the users who need ERP access are set up.
Why it matters. Branch openings become repeatable, controls are consistent, and the business can see a new branch's performance from its first week.
Core apps
Optional but recommended
- Purchase So reordering starts from real stock.
- Documents So delivery notes and bills are captured, not typed.
- Sign So quotes are accepted and signed online.
How TRC delivers it
- Standard in Odoo Branches, multiple warehouses and shared products and price lists.
- Standard in Odoo · TRC configures Access groups by role and analytic accounts for branch reporting.
- TRC connects Connection to a retained payroll or HR system where one exists.
What we would prove before you commit
- Create a test branch from the template and show sales, stock and reporting working on day one.
- Confirm a branch user cannot see other branches' restricted data.
Odoo 20 documentation: Multi-company and branches (Odoo 20.0) opens odoo.com ↗ · Analytic accounting (Odoo 20.0) opens odoo.com ↗ · Reordering rules (Odoo 20.0) opens odoo.com ↗
Open this journey on its own page
Can this delivery date be supported by available or incoming supply?
Supplier delays an incoming delivery. The forecast changes, and affected orders can be found so customers are told before the date passes.
The objective. The sales rep wants to see available and incoming stock while quoting, and give a date based on the same information the warehouse uses.
How the work flows
- Sales rep Checks forecast availability for each product while building the quotation, including stock on order or in production.
- Sales rep Sets a delivery date or promises from expected availability, visible on the quotation. Decision: Can this delivery date be supported by available or incoming supply?
- Customer Confirms the order.
- Warehouse or planner Sees the confirmed demand in the same forecast and adjusts priorities if needed.
- System Reserves stock or triggers replenishment based on rules.
- Sales manager Reviews orders at risk of missing their promised date and contacts customers early.
What must stay connected
- On-hand, reserved and incoming stock
- Promised delivery date
- Replenishment orders
- Orders at risk
When it doesn't go to plan
Supplier delays an incoming delivery
The forecast changes, and affected orders can be found so customers are told before the date passes.
Planning is done in a retained specialist scheduling tool
Availability from that tool is fed in by integration, and the ERP remains the place sales checks.
Why it matters. Promises are based on shared information, fewer internal calls are needed, and late orders are identified while there is still time to act.
Core apps
Optional but recommended
- Sign So quotes are accepted and signed online.
- CRM So every quote starts from the opportunity.
- Documents So delivery notes and bills are captured, not typed.
How TRC delivers it
- Standard in Odoo Forecasted stock reporting and lead times across sales, purchase and manufacturing.
- Standard in Odoo · TRC configures Replenishment rules and delivery lead times by product.
- TRC connects Integration with a retained planning tool where the business keeps one.
What we would prove before you commit
- Quote test products with stock, incoming purchase and production and compare promised dates.
- Delay a test receipt and show which orders become at risk.
Odoo 20 documentation: Forecasted stock (Odoo 20.0) opens odoo.com ↗ · Lead times (Odoo 20.0) opens odoo.com ↗
Open this journey on its own page
Is this margin acceptable, and are its costs current?
Supplier cost increases mid-month. Updated cost flows into new quotations, and the effect on open orders can be reviewed.
The objective. Finance and sales want to see expected margin on each quotation and actual margin by customer as orders are invoiced.
How the work flows
- Sales rep Sees margin on the quotation based on product cost, with a warning set for low-margin lines.
- Sales manager Approves orders below the agreed margin threshold before confirmation. Decision: Is this margin acceptable, and are its costs current?
- Warehouse Records deliveries; inventory valuation updates cost of goods as stock moves.
- Finance Records freight and other costs with analytic distribution to the customer or order.
- Finance and sales Review margin by customer and product weekly from live reports.
What must stay connected
- Product cost
- Quotation margin
- Approval of low-margin orders
- Analytic costs by customer
- Actual margin as invoiced
When it doesn't go to plan
Supplier cost increases mid-month
Updated cost flows into new quotations, and the effect on open orders can be reviewed.
Costs arrive after invoicing
Late bills are allocated to the customer analytically so margin is corrected rather than lost in overheads.
Why it matters. Margin problems surface while orders can still be repriced or renegotiated, not after the month is closed.
Core apps
Optional but recommended
- Sign So quotes are accepted and signed online.
- CRM So every quote starts from the opportunity.
- Expenses So claims are approved and posted, not re-keyed.
How TRC delivers it
- Standard in Odoo Margin on quotations, inventory valuation and analytic accounting.
- Standard in Odoo · TRC configures Approval rule for orders under a margin threshold.
- Standard in Odoo · TRC configures Weekly margin report by customer and product.
What we would prove before you commit
- Show a test quotation below threshold blocked until approved.
- Show margin by customer moving as test deliveries and late costs are recorded.
Odoo 20 documentation: Quotation margin (Odoo 20.0) opens odoo.com ↗ · Analytic accounting (Odoo 20.0) opens odoo.com ↗ · Inventory valuation (Odoo 20.0) opens odoo.com ↗
Open this journey on its own page
Which manual transfers should be integrated, retained or removed?
A retained system changes its data format. The integration fails visibly into the exception queue rather than creating bad records.
The objective. The business wants information to move between its systems by agreed rules, with exceptions visible to a team rather than held by one person.
How the work flows
- Operations lead Maps which system owns each piece of information and which manual transfers exist today.
- TRC and the business Agree which systems are retained and which transfers are replaced by integration or by moving the process into the ERP. Decision: Which manual transfers should be integrated, retained or removed?
- System Receives records from retained systems through connectors or webhooks and creates orders or entries.
- System Flags records that fail validation into a queue with the reason.
- Operations team Works the exception queue, with any team member able to resolve items.
- Operations lead Reviews volumes and recurring failures to improve the rules.
What must stay connected
- Ownership of each record by system
- Integration rules
- Exception queue and reasons
- Audit of what was created and when
When it doesn't go to plan
A retained system changes its data format
The integration fails visibly into the exception queue rather than creating bad records.
Integration is not worth building for a low-volume transfer