The right item, in the right place, bought and moved correctly

One Item, one Vendor, one Asset, one history

Operations brings seven modules onto the same shared records. Inventory, Procurement, Manufacturing, Field Service, Commerce and Finance all read and write one Item master, one Organization record in a vendor, customer or carrier role, and one Asset record. No module keeps its own copy. A goods receipt creates a stock move, a vendor bill is matched against the purchase order and the receipt, a manufacturing order consumes components and produces finished stock, and an asset's maintenance work order is executed by a field technician using parts from van stock.

Every physical-world change is a typed Action

Posting a stock move, issuing a purchase order, accepting a supplier change, releasing a batch from quality hold, generating an e-way bill or dispatching a technician runs through the One3 Kernel Action Bus. Each Action carries a risk tier, a reversibility class and your delegation-of-authority limits. People, integrations, MCP clients and Digital Employees use the same Actions and the same checks, and every one is written to a hash-chained audit log. Posted documents are never edited in place; corrections are reversal or amendment Actions with version history.

The frontline works where it already works

Suppliers are designed to confirm purchase orders on WhatsApp. Storekeepers record goods receipts with a photo of the delivery note or a voice note. Drivers capture proof of delivery on a phone, and technicians complete checklists offline in basements with no signal. Voice and text in Indian languages turn into proposed changes that a person approves in one tap; they never post directly unless the Action and the agent's earned autonomy allow it.

India compliance as part of the product

GST-correct stock documents, delivery and job-work challans, the e-way bill lifecycle tied to shipments and trips, and e-invoice through the shared Tax Engine are planned as product features, not a configuration project. Every regulatory rule is read from the Fact Register and must be verified before build; a stale fact blocks the dependent Action with a clear message.

How it fits with the rest of One3

• Finance owns Accounts, the Tax Engine, Billing and Payments Hub. Stock valuation, depreciation and manufacturing cost post to Accounts, and payment approval stays an R4 human decision.
• Commerce shares the Item master and reserves stock in Inventory for online, POS and WhatsApp orders.
• Service Desk tickets can become field service requests.
• AI Workforce supplies the rentable Operations Digital Employees, and their outcomes are recorded in the Investment & ROI Ledger against baselines captured at onboarding.
• Migration Factory is planned to move items, balances, open POs and assets from Tally, Zoho Inventory, ERPNext, Odoo and spreadsheets with a reconciled cut-over.

Availability

Operations is outside the Year-1 Product Boundary. Inventory & Warehouse and Procurement are the first modules, planned for W4 (Year 3, PI-5), followed by Assets & Maintenance and Field Service in PI-6. Supply Chain & Logistics, Manufacturing & Quality and Fleet are planned for W5. Until then, teams keep their existing tools.