Light Manufacturing OS: A Guided Demo.

This is a guided demo of Light Manufacturing OS, for a company that assembles goods, sells them on more than one channel and ships them through a 3PL. What you will see is one surface: our screens over Zoho Inventory, Books and CRM, the storefront and the 3PL, with an AI control plane in a pane on every screen. The planner talks or clicks on the same screen; the floor uses Cliq or Slack on a phone. It reads every system, decides against the company's operating model, acts through the applications' own APIs, and asks a person only where a person should decide.

A person approves every purchase order. Everything on screen is a mock-up of the solution with sample data, drawn as our own screens in our brand rather than the Zoho interface. The company, the vendors, the product and every figure are invented. It is seven in the morning. m. The planner has typed nothing. The control plane read stock by warehouse, open sales orders, each vendor's delivered lead time and the terms on file, and posted its morning proposal in the planning channel: Warehouse B goes short on three items inside lead time.

One gate per vendor. Northline Steel, six lines of brackets, two thousand one hundred and forty dollars, because the 12-inch kit is selling eleven a day and the brackets take nine days. Harbor Fasteners, five lines, six hundred and ninety. Pell Packaging, three lines, one thousand nine hundred and ninety. Every line carries its quantity, its cost and its reason. The planner replies 1, 1, 2. Two purchase orders are created in Zoho Inventory and sent to the vendors. The third is held with a note asking for a smaller quantity.

The read-back names the PO numbers; the run log names who approved them. Nobody opened Inventory. The spend gate was a person. On the floor, the supervisor types: Build 40 of the 12-inch kit for the Acme order. The plane checks the bill of materials against stock in Warehouse B. Brackets, panels and packaging are there. Fasteners are short: enough for twenty-eight kits, and the rest of the Harbor Fasteners order lands Thursday. It answers with a choice. One, build twenty-eight now and twelve on Thursday's receipt, and Acme's promise date holds.

Two, substitute the longer fastener from Warehouse A and build all forty today. Three, wait. The supervisor replies 1. The assembly is booked in Zoho Inventory for twenty-eight units, the components are issued from stock, a second assembly is scheduled against Thursday's receipt, and the floor channel gets the pick list and the start time. The unit cost is what went into it, the labor step included. The floor talked. The system booked. Overnight, forty-one orders landed from the storefront, and nobody allocated them. The plane allocated each by rule: the stock nearest the customer, oldest order first, the item by its part number.

It sent the pick requests to the 3PL with the packaging rules, and watched for the confirmations. As each came back with its shipped quantity, tracking number and carrier, it updated the order in Zoho CRM and sent the customer the tracking on the channel they bought from. Forty orders ran without a person. One did not. Order 10482 needs six of the 12-inch kit and the 3PL holds four. That exception arrived in the channel as a gate: ship four now and two on Thursday, ship complete on Thursday, or offer the 18-inch kit at the same price.

The customer team replied 1, and the partial went out recorded as partial. Hours to minutes, and a person saw only the exception. Thursday. The 3PL's email says: receipt for PO 1182, short by six cases. The plane reads the email and records the receipt against the purchase order in Inventory, four hundred and ninety-four of five hundred. It matches Northline's bill in Zoho Books to what arrived, not to what was ordered. The variance is over the threshold, so it comes to chat as a gate: pay the bill short, or hold it and ask Northline for the six cases.

The planner replies 2. The bill is held in Books, the note goes to the vendor, and stock rises by what actually came in. Three facts agree: what was ordered, what arrived, what is owed. Nobody keyed a receipt. Friday. The owner asks: What did we make on the storefront last week, and what should we stop? The plane answers from the daily margin table it writes for every SKU, order and channel: landed cost from the receipts and the bills, the 3PL fees, the carrier, the ad cost from the marketing plane, and the price the customer paid.

The 12-inch kit earned thirty-one percent on the storefront and nineteen on the marketplace. The 6-inch kit lost money on the marketplace every day of the week once the 3PL's per-order fee was counted. The weekly rule it derives: stop the 6-inch kit on the marketplace, keep it on the storefront, and raise the marketplace price on the 18-inch kit, where margin held above target. Each rule is a gate. The owner's 1 changes the listings; a 2 keeps the rule as a note. The number the owner sees is the real one, and it is a day old, not a month.

That was one week in a plant that talks to its systems instead of typing into them. There is a ladder. Configured applications: Zoho set up, your people working in the screens. Integrated business solutions: the applications joined, the storefront and the 3PL connected, the data flowing, people still acting in the screens. AI-driven integrated business solutions: the same joined applications, operated by a control plane that observes, decides and acts, with every action logged and every money gate yours. One surface: the pane on every screen, the controls beside it, and every money gate yours.

We are CodeStringers, a Zoho consulting and integration partner. Light Manufacturing OS runs on your own accounts. Your planner talks to it. It acts, in Inventory, Books, CRM and at the 3PL. You approve the purchase orders. The no-risk discovery starts with your operations as they are.