ERP turnaround · Odoo across 4 countries
Newmatic Kitchens: four countries running on one rebuilt Odoo ERP
Published · Updated
A prior vendor left the ERP in disarray: accounting flows broken, inventory nobody trusted, and access confusion between country entities. KoderXpert rebuilt the whole Odoo environment across Singapore, Malaysia, Indonesia and Kenya, and cut order processing time by 40%.
Designed, built and delivered by KoderXpert Technologies Pvt. Ltd.
Official Odoo Ready Partner · Ahmedabad & Gandhinagar, India
- Client
- Newmatic Kitchens
- Industry
- Kitchen appliances & equipment
- Platform
- Odoo ERP, multi-company & multi-currency
- Implementation partner
- KoderXpert Technologies
- Headline result
- 40% faster order processing
01 · Overview
The 30-second version
- Newmatic Kitchens is a premium global kitchen appliance brand: ovens, hobs, hoods, sinks and accessories, sold and serviced across Singapore, Malaysia, Indonesia and Kenya.
- A prior vendor left their Odoo ERP broken: accounting in disarray, inventory data nobody trusted, no approval workflows, weak access control and no verification for order pickups.
- KoderXpert rebuilt the environment from the ground up: multi-currency accounting, barcode inventory, approval workflows, OTP and SMS pickup verification, and role-based access, cutting order processing time by 40%.
02 · Inheriting a broken ERP
What was going wrong before Odoo?
Six ways the old setup was burning the kitchen
A prior vendor's implementation left every core flow either broken or missing, across all four country entities.
Broken accounting
Accounting flows left in disarray, with no clean company separation or currency handling.
The cost → books nobody could sign offUnreliable inventory
Stock data could not be trusted across warehouses, so planning ran on guesswork.
The cost → stockouts and dead stockMulti-company confusion
Access blurred between the four country entities, with data visible where it should not be.
The cost → cross-country data leaksNo approvals
Sales, inventory and finance transactions moved with no sign-off from anyone.
The cost → zero accountabilityWeak access control
Poor user access controls across the organization, with permissions nobody had designed.
The cost → a compliance risk on legsNo pickup verification
No OTP or notification system for order pickups, so handovers ran on trust alone.
The cost → disputes at the counter03 · The turnaround
Drag it and see the before & after yourself
Slide the orange handle. Left is the broken setup they inherited, right is life after the rebuild.
- ✗ Accounting flows broken, books in disarray
- ✗ Stock counts nobody trusted, in any warehouse
- ✗ Country entities seeing each other's data
- ✗ Sales, stock & finance moving with no sign-off
- ✗ Order pickups handed over on trust alone
the broken-ERP era 😵
one clean ERP ✨
- ✔ Audit-ready books across all four countries
- ✔ Barcode-tracked stock, live in every warehouse
- ✔ Each entity sees exactly its own data, no more
- ✔ Every sensitive transaction needs a sign-off
- ✔ Every pickup OTP-verified, customer SMS sent
← drag toward the mess · drag toward the rebuild →
04 · The plan
What "fixed" had to actually mean
Six outcomes agreed with the Newmatic team before touching the system. Hover any goal to tick it off.
Rebuild the Odoo setup to reflect real-world, multi-country operations.
Multi-currency accounting that holds up across companies and audits.
Real-time inventory with live tracking & warehouse control.
Approval workflows for sales, inventory & finance transactions.
OTP verification for order pickups & customer confirmations.
Role-based security with clear, scoped access for every user group.
05 · What we delivered
What did KoderXpert build?
Six capabilities, one rebuilt ERP
KoderXpert rebuilt the Odoo environment from the ground up: accounting, inventory, access and customer notifications, all realigned to how Newmatic actually operates.
Accounting overhaul
Restructured with proper company separation, journals and currency management. Chart of accounts rebuilt on an audit-ready foundation for true multi-currency, multi-company operations.
books the auditors loveReal-time inventory
Barcode scanning tied directly into stock movements, with warehouse operations visible live across every site. A shared foundation for planning, replenishment and reporting.
no more guesswork stockMulti-company access rules
Access scoped precisely to each user's company and role. Cross-company visibility blocked where it is not appropriate, without slowing down daily operations.
four entities, zero leaksCustom approval workflows
Structured approvals across sales, inventory, purchase and accounting. Nothing moves forward without the right sign-off, with full visibility into where each request stands.
nothing slips throughOTP & SMS system
OTP verification confirms every order pickup, automated SMS confirmations go straight to customers, and a localized SMS gateway is configured for each country.
every pickup, verifiedRedesigned access rights
Role-based permissions rebuilt from the ground up, a stronger compliance posture across all entities, and easier day-to-day usability for every user group.
secure and simpler06 · Functional deep dive
How the rebuilt ERP actually works
The delivery summary says what was rebuilt. This is the functional detail underneath: how four countries share one system without sharing each other's data, and how the core flows run now.
Four countries, one system, clean walls
Multi-company architecture gives each entity its own books and stock inside one shared platform.
- Company-scoped records: each country's transactions, customers and stock belong to its entity, with access rules enforcing the walls.
- Shared master data: products and group-level records stay consistent across entities instead of drifting apart.
- Group visibility: leadership consolidates across countries while each team works only in its own scope.
The accounting overhaul
The books were rebuilt until every entity's numbers could be trusted.
- Rebuilt configuration: charts, taxes and journals corrected per country's requirements.
- Clean postings: sales, purchases and stock moves post their own entries, ending manual correction cycles.
- Trustworthy reporting: entity and consolidated views read the same live records.
Real-time inventory across entities
Stock stopped being a guess in every warehouse.
- Live quantities: every movement updates stock in real time, per warehouse and per company.
- Inter-company flows: goods moving between entities follow documented flows with both sides posted correctly.
- Availability that sells: sales teams quote from real stock, which is a large part of the 40% faster order processing.
Approvals, OTP & SMS localization
Workflow controls and country-specific communications were built into the core flows.
- Custom approval workflows: orders and spend route through defined approvers per entity.
- Localized OTP & SMS: verification and notifications run through per-country gateways, matching local carriers and formats.
- Redesigned access rights: roles were rebuilt from scratch so every user sees exactly their job, and nothing else.
Walls for entities, windows for leadership
Record rules scope every transaction, customer and stock record to its owning company, users work only inside their entity, and group-level roles consolidate across all four countries from the same live records.
07 · How we built it
How was the Odoo project delivered?
From audit to go-live, course by course
Six stages, starting with an honest audit of the broken setup and ending with a phased, supported go-live across four countries.
Audit & gap analysis find the burn marks
A full audit of the inherited setup across accounting, inventory and access, mapping exactly where the prior implementation broke down.
System redesign draw the new floor plan
Company structure, chart of accounts, warehouses and access model redesigned around how the four entities really operate.
Feature enhancement build what was missing
Approval workflows, barcode inventory, OTP verification and localized SMS gateways built on top of the corrected foundation.
Data cleanup & migration scrub every pan
Legacy data cleaned, reconciled and migrated so the new environment started trustworthy from day one.
User training & UAT taste before serving
Hands-on training for every user group and end-to-end acceptance testing across all four countries.
Go-live & support service is open
Phased go-live with close support until the rebuilt ERP became the everyday habit in every entity.
08 · Engineering notes
The technical decisions behind the turnaround
For the technically curious: how the work was engineered so it survives upgrades, audits and time.
Custom addons, zero core edits
Everything KoderXpert built lives in namespaced custom modules (kx_multico_rules · kx_acct_rebuild · kx_otp_sms · kx_access_redesign) on Python and the Odoo ORM.
- Inheritance, not modification: models and views are extended through Odoo's inheritance mechanisms, never edited in core, so future Odoo upgrades do not bury the work.
- Configuration as data: company rules, charts, approval chains and gateway settings ship as XML data records per entity, reproducible and reviewable.
- PostgreSQL underneath: one database as the single source of truth, so no exports or reconciliation jobs exist between the moving parts.
The data migration pipeline
The riskiest part of the project was the data: the prior vendor's broken configuration and its inconsistent historical records across four entities. It moved through a staged pipeline, not a bulk import.
- Extract & cleanse: legacy records exported, deduplicated and normalized in a staging environment before anything touched production.
- Ordered loading: corrections and reloads run entity by entity in dependency order: charts and taxes, partners and products, stock quantities, then open documents, via the ORM with balances verified per company.
- Verified before sign-off: record counts and key balances checked against the source system, with every opening figure posted as an auditable entry.
Reports, automation & performance
Dashboards and documents are native Odoo artifacts reading live data, so they inherit access rules and never go stale.
- QWeb & OWL: printable documents render through QWeb templates; on-screen dashboards read aggregated, indexed queries that stay fast as volume grows.
- Scheduled automation: scheduled jobs refresh consolidated dashboards, monitor gateway deliveries and flag inter-company documents awaiting their counterpart.
- Filters built in: period, location and team filters are part of the report definitions, so answering a leadership question is one click, not a new spreadsheet.
Testing, cutover & hardening
The rollout landed on a live business, so it was engineered to be boring.
- Staging mirror: every change proven on a copy of the real database before reaching production.
- Role-based UAT: each country's team walked scripted order-to-cash and procure-to-pay journeys in its own entity, plus inter-company scenarios, before phased go-live.
- Access hardening: group permissions and record rules reviewed role by role, so each team sees exactly what its job requires.
- Documented handover: configuration, roles and workflows documented so the system's logic belongs to the client, not to anyone's memory.
Localization built into the flow
Verification and notifications run through per-country OTP and SMS gateways matched to local carriers and formats, so an order in any market confirms, communicates and ships without a workaround.
09 · The impact
What changed after go-live?
The results, in numbers
the part clients screenshot ↓- Accurate, compliant accounting across all 4 countries
- Real-time inventory visibility: fewer stockouts, better planning
- Improved operational security through access controls & approvals
- Cross-company data cleanly separated between entities
- Higher user satisfaction from better usability
- Mobile-ready notifications customers actually receive
10 · Under the hood
Technologies & core skills
"We were struggling with a broken ERP setup that was costing us time and money. KoderXpert not only fixed everything but transformed our operations completely. From multi-country accounting to OTP order verifications, everything works like a charm now. Truly grateful for their support and expertise."
11 · Quick questions, honest answers
Thinking about a similar build?
Yes. Newmatic runs four country entities on one platform: each has its own books, stock and access walls, master data stays shared and consistent, and leadership consolidates across all of them.
The way this turnaround ran: audit the damage entity by entity, rebuild accounting configuration, reload clean data with verified balances, re-wire stock to post in real time, and redesign access from scratch.
Record rules scope every transaction, customer and stock record to its owning company, so users work only inside their entity while group-level roles see consolidated views.
Goods and services moving between entities follow documented flows that post correctly on both sides, with pending counterpart documents flagged automatically.
Verification and customer notifications run through per-country gateways matched to local carriers and formats, so communications actually deliver in every market.
From removing friction across the flow: real-time stock lets sales quote honestly, approvals route themselves, postings stop needing manual correction, and access is scoped so nobody wades through someone else's data.
No. Work ran entity by entity with staged corrections, verified balances and phased go-lives, so the four countries kept trading throughout the turnaround.
Yes. Any group running several country entities on one ERP benefits from the same pattern: clean multi-company walls, shared masters, real-time stock and per-country localization.
Yes, by design. All of KoderXpert's work for Newmatic Kitchens lives in namespaced custom addons that extend Odoo through inheritance; the core is never edited, and configuration ships as data records, making the setup reproducible and upgrade-safe.
It is the riskiest part, which is why it runs as a staged pipeline: extract and cleanse in a staging environment, load in dependency order through the Odoo ORM so business rules still apply, then verify counts and balances against the source before sign-off.
It depends on scope, which is why delivery ran in structured phases from discovery to supported go-live. Mapping the real process first fixes the scope before any build starts, and phased rollout keeps the business running throughout.
KoderXpert is an Odoo partner that maps the real process before building, engineers upgrade-safe custom modules with zero core edits, and delivers measurable outcomes: for Newmatic Kitchens, four countries running one rebuilt ERP with 40% faster order processing. Talk to KoderXpert about your project.
Struggling with a broken ERP setup?
Tell us where your accounting, inventory and access controls stand today. KoderXpert will show you what a clean, audit-ready Odoo rebuild looks like for your operation.
Related case studies
- Elumatec: Odoo ERP audit and refactoringInherited ERP audited then rebuilt for UAE VAT
- Matahin: Odoo supply chain ERP implementationProcurement to export with batch traceability
- Kamakhya Pipes: Odoo manufacturing ERP implementationShop-floor hardware wired into production and stock
ERP turnaround · Odoo across 4 countries
Newmatic Kitchens: four countries running on one rebuilt Odoo ERP
Published · Updated
A prior vendor left the ERP in disarray: accounting flows broken, inventory nobody trusted, and access confusion between country entities. KoderXpert rebuilt the whole Odoo environment across Singapore, Malaysia, Indonesia and Kenya, and cut order processing time by 40%.
Designed, built and delivered by KoderXpert Technologies Pvt. Ltd.
Official Odoo Ready Partner · Ahmedabad & Gandhinagar, India
- Client
- Newmatic Kitchens
- Industry
- Kitchen appliances & equipment
- Platform
- Odoo ERP, multi-company & multi-currency
- Implementation partner
- KoderXpert Technologies
- Headline result
- 40% faster order processing
01 · Overview
The 30-second version
- Newmatic Kitchens is a premium global kitchen appliance brand: ovens, hobs, hoods, sinks and accessories, sold and serviced across Singapore, Malaysia, Indonesia and Kenya.
- A prior vendor left their Odoo ERP broken: accounting in disarray, inventory data nobody trusted, no approval workflows, weak access control and no verification for order pickups.
- KoderXpert rebuilt the environment from the ground up: multi-currency accounting, barcode inventory, approval workflows, OTP and SMS pickup verification, and role-based access, cutting order processing time by 40%.
02 · Inheriting a broken ERP
What was going wrong before Odoo?
Six ways the old setup was burning the kitchen
A prior vendor's implementation left every core flow either broken or missing, across all four country entities.
Broken accounting
Accounting flows left in disarray, with no clean company separation or currency handling.
The cost → books nobody could sign offUnreliable inventory
Stock data could not be trusted across warehouses, so planning ran on guesswork.
The cost → stockouts and dead stockMulti-company confusion
Access blurred between the four country entities, with data visible where it should not be.
The cost → cross-country data leaksNo approvals
Sales, inventory and finance transactions moved with no sign-off from anyone.
The cost → zero accountabilityWeak access control
Poor user access controls across the organization, with permissions nobody had designed.
The cost → a compliance risk on legsNo pickup verification
No OTP or notification system for order pickups, so handovers ran on trust alone.
The cost → disputes at the counter03 · The turnaround
Drag it and see the before & after yourself
Slide the orange handle. Left is the broken setup they inherited, right is life after the rebuild.
- ✗ Accounting flows broken, books in disarray
- ✗ Stock counts nobody trusted, in any warehouse
- ✗ Country entities seeing each other's data
- ✗ Sales, stock & finance moving with no sign-off
- ✗ Order pickups handed over on trust alone
the broken-ERP era 😵
one clean ERP ✨
- ✔ Audit-ready books across all four countries
- ✔ Barcode-tracked stock, live in every warehouse
- ✔ Each entity sees exactly its own data, no more
- ✔ Every sensitive transaction needs a sign-off
- ✔ Every pickup OTP-verified, customer SMS sent
← drag toward the mess · drag toward the rebuild →
04 · The plan
What "fixed" had to actually mean
Six outcomes agreed with the Newmatic team before touching the system. Hover any goal to tick it off.
Rebuild the Odoo setup to reflect real-world, multi-country operations.
Multi-currency accounting that holds up across companies and audits.
Real-time inventory with live tracking & warehouse control.
Approval workflows for sales, inventory & finance transactions.
OTP verification for order pickups & customer confirmations.
Role-based security with clear, scoped access for every user group.
05 · What we delivered
What did KoderXpert build?
Six capabilities, one rebuilt ERP
KoderXpert rebuilt the Odoo environment from the ground up: accounting, inventory, access and customer notifications, all realigned to how Newmatic actually operates.
Accounting overhaul
Restructured with proper company separation, journals and currency management. Chart of accounts rebuilt on an audit-ready foundation for true multi-currency, multi-company operations.
books the auditors loveReal-time inventory
Barcode scanning tied directly into stock movements, with warehouse operations visible live across every site. A shared foundation for planning, replenishment and reporting.
no more guesswork stockMulti-company access rules
Access scoped precisely to each user's company and role. Cross-company visibility blocked where it is not appropriate, without slowing down daily operations.
four entities, zero leaksCustom approval workflows
Structured approvals across sales, inventory, purchase and accounting. Nothing moves forward without the right sign-off, with full visibility into where each request stands.
nothing slips throughOTP & SMS system
OTP verification confirms every order pickup, automated SMS confirmations go straight to customers, and a localized SMS gateway is configured for each country.
every pickup, verifiedRedesigned access rights
Role-based permissions rebuilt from the ground up, a stronger compliance posture across all entities, and easier day-to-day usability for every user group.
secure and simpler06 · Functional deep dive
How the rebuilt ERP actually works
The delivery summary says what was rebuilt. This is the functional detail underneath: how four countries share one system without sharing each other's data, and how the core flows run now.
Four countries, one system, clean walls
Multi-company architecture gives each entity its own books and stock inside one shared platform.
- Company-scoped records: each country's transactions, customers and stock belong to its entity, with access rules enforcing the walls.
- Shared master data: products and group-level records stay consistent across entities instead of drifting apart.
- Group visibility: leadership consolidates across countries while each team works only in its own scope.
The accounting overhaul
The books were rebuilt until every entity's numbers could be trusted.
- Rebuilt configuration: charts, taxes and journals corrected per country's requirements.
- Clean postings: sales, purchases and stock moves post their own entries, ending manual correction cycles.
- Trustworthy reporting: entity and consolidated views read the same live records.
Real-time inventory across entities
Stock stopped being a guess in every warehouse.
- Live quantities: every movement updates stock in real time, per warehouse and per company.
- Inter-company flows: goods moving between entities follow documented flows with both sides posted correctly.
- Availability that sells: sales teams quote from real stock, which is a large part of the 40% faster order processing.
Approvals, OTP & SMS localization
Workflow controls and country-specific communications were built into the core flows.
- Custom approval workflows: orders and spend route through defined approvers per entity.
- Localized OTP & SMS: verification and notifications run through per-country gateways, matching local carriers and formats.
- Redesigned access rights: roles were rebuilt from scratch so every user sees exactly their job, and nothing else.
Walls for entities, windows for leadership
Record rules scope every transaction, customer and stock record to its owning company, users work only inside their entity, and group-level roles consolidate across all four countries from the same live records.
07 · How we built it
How was the Odoo project delivered?
From audit to go-live, course by course
Six stages, starting with an honest audit of the broken setup and ending with a phased, supported go-live across four countries.
Audit & gap analysis find the burn marks
A full audit of the inherited setup across accounting, inventory and access, mapping exactly where the prior implementation broke down.
System redesign draw the new floor plan
Company structure, chart of accounts, warehouses and access model redesigned around how the four entities really operate.
Feature enhancement build what was missing
Approval workflows, barcode inventory, OTP verification and localized SMS gateways built on top of the corrected foundation.
Data cleanup & migration scrub every pan
Legacy data cleaned, reconciled and migrated so the new environment started trustworthy from day one.
User training & UAT taste before serving
Hands-on training for every user group and end-to-end acceptance testing across all four countries.
Go-live & support service is open
Phased go-live with close support until the rebuilt ERP became the everyday habit in every entity.
08 · Engineering notes
The technical decisions behind the turnaround
For the technically curious: how the work was engineered so it survives upgrades, audits and time.
Custom addons, zero core edits
Everything KoderXpert built lives in namespaced custom modules (kx_multico_rules · kx_acct_rebuild · kx_otp_sms · kx_access_redesign) on Python and the Odoo ORM.
- Inheritance, not modification: models and views are extended through Odoo's inheritance mechanisms, never edited in core, so future Odoo upgrades do not bury the work.
- Configuration as data: company rules, charts, approval chains and gateway settings ship as XML data records per entity, reproducible and reviewable.
- PostgreSQL underneath: one database as the single source of truth, so no exports or reconciliation jobs exist between the moving parts.
The data migration pipeline
The riskiest part of the project was the data: the prior vendor's broken configuration and its inconsistent historical records across four entities. It moved through a staged pipeline, not a bulk import.
- Extract & cleanse: legacy records exported, deduplicated and normalized in a staging environment before anything touched production.
- Ordered loading: corrections and reloads run entity by entity in dependency order: charts and taxes, partners and products, stock quantities, then open documents, via the ORM with balances verified per company.
- Verified before sign-off: record counts and key balances checked against the source system, with every opening figure posted as an auditable entry.
Reports, automation & performance
Dashboards and documents are native Odoo artifacts reading live data, so they inherit access rules and never go stale.
- QWeb & OWL: printable documents render through QWeb templates; on-screen dashboards read aggregated, indexed queries that stay fast as volume grows.
- Scheduled automation: scheduled jobs refresh consolidated dashboards, monitor gateway deliveries and flag inter-company documents awaiting their counterpart.
- Filters built in: period, location and team filters are part of the report definitions, so answering a leadership question is one click, not a new spreadsheet.
Testing, cutover & hardening
The rollout landed on a live business, so it was engineered to be boring.
- Staging mirror: every change proven on a copy of the real database before reaching production.
- Role-based UAT: each country's team walked scripted order-to-cash and procure-to-pay journeys in its own entity, plus inter-company scenarios, before phased go-live.
- Access hardening: group permissions and record rules reviewed role by role, so each team sees exactly what its job requires.
- Documented handover: configuration, roles and workflows documented so the system's logic belongs to the client, not to anyone's memory.
Localization built into the flow
Verification and notifications run through per-country OTP and SMS gateways matched to local carriers and formats, so an order in any market confirms, communicates and ships without a workaround.
09 · The impact
What changed after go-live?
The results, in numbers
the part clients screenshot ↓- Accurate, compliant accounting across all 4 countries
- Real-time inventory visibility: fewer stockouts, better planning
- Improved operational security through access controls & approvals
- Cross-company data cleanly separated between entities
- Higher user satisfaction from better usability
- Mobile-ready notifications customers actually receive
10 · Under the hood
Technologies & core skills
"We were struggling with a broken ERP setup that was costing us time and money. KoderXpert not only fixed everything but transformed our operations completely. From multi-country accounting to OTP order verifications, everything works like a charm now. Truly grateful for their support and expertise."
11 · Quick questions, honest answers
Thinking about a similar build?
Yes. Newmatic runs four country entities on one platform: each has its own books, stock and access walls, master data stays shared and consistent, and leadership consolidates across all of them.
The way this turnaround ran: audit the damage entity by entity, rebuild accounting configuration, reload clean data with verified balances, re-wire stock to post in real time, and redesign access from scratch.
Record rules scope every transaction, customer and stock record to its owning company, so users work only inside their entity while group-level roles see consolidated views.
Goods and services moving between entities follow documented flows that post correctly on both sides, with pending counterpart documents flagged automatically.
Verification and customer notifications run through per-country gateways matched to local carriers and formats, so communications actually deliver in every market.
From removing friction across the flow: real-time stock lets sales quote honestly, approvals route themselves, postings stop needing manual correction, and access is scoped so nobody wades through someone else's data.
No. Work ran entity by entity with staged corrections, verified balances and phased go-lives, so the four countries kept trading throughout the turnaround.
Yes. Any group running several country entities on one ERP benefits from the same pattern: clean multi-company walls, shared masters, real-time stock and per-country localization.
Yes, by design. All of KoderXpert's work for Newmatic Kitchens lives in namespaced custom addons that extend Odoo through inheritance; the core is never edited, and configuration ships as data records, making the setup reproducible and upgrade-safe.
It is the riskiest part, which is why it runs as a staged pipeline: extract and cleanse in a staging environment, load in dependency order through the Odoo ORM so business rules still apply, then verify counts and balances against the source before sign-off.
It depends on scope, which is why delivery ran in structured phases from discovery to supported go-live. Mapping the real process first fixes the scope before any build starts, and phased rollout keeps the business running throughout.
KoderXpert is an Odoo partner that maps the real process before building, engineers upgrade-safe custom modules with zero core edits, and delivers measurable outcomes: for Newmatic Kitchens, four countries running one rebuilt ERP with 40% faster order processing. Talk to KoderXpert about your project.
Struggling with a broken ERP setup?
Tell us where your accounting, inventory and access controls stand today. KoderXpert will show you what a clean, audit-ready Odoo rebuild looks like for your operation.
Related case studies
- Elumatec: Odoo ERP audit and refactoringInherited ERP audited then rebuilt for UAE VAT
- Matahin: Odoo supply chain ERP implementationProcurement to export with batch traceability
- Kamakhya Pipes: Odoo manufacturing ERP implementationShop-floor hardware wired into production and stock
