Routings and work centres, a real shop-floor terminal, batch and individual-serial traceability in both directions, and order costing that settles against standards — on one stock ledger shared with purchasing, sales and accounts.
When a customer reports a failure, the question is which raw material lot went into that unit and what else was built from it. Without genealogy recorded at consumption time, answering takes days of paper and the recall is scoped by guesswork — always far wider than it needed to be.
Purchase says one number, the shop floor says another, and accounts value a third. It happens whenever issues to production are recorded separately from the stock ledger instead of moving it.
Without routings carrying setup and run times per work centre, there is no capacity figure, no OEE, and no way to say whether a job that took nine hours should have taken six.
The classic estimating error: a 30-minute setup applied per piece turns a 500-unit order into ten days of phantom capacity, and quotes get padded to cover a load that was never real.
Material sent to a subcontractor stays your inventory and your GST liability. Tracked on a WhatsApp thread, ITC-04 becomes a quarterly reconstruction and challans time out unnoticed.
If scrap is not a stock movement it is not a cost, and the first time anyone sees the number is in a year-end variance nobody can decompose.
| Business requirement | Rebota capability | Relevance | Status |
|---|---|---|---|
| Bill of Materials | Multi-level BOM, explode ("what does 250 consume") and where-used ("what is this part in") | High | Available |
| Routings & Work Centres | Operations with setup, run, wait and move times, subcontracted steps, QC flags | High | Available |
| Shop-Floor Capture | Operator terminal — start, pause with reason code, report good and scrap quantity | High | Available |
| OEE | Availability, performance and quality computed from captured time against routing standards | High | Available |
| Batch Traceability | Batch lots with expiry and FEFO consumption | High | Available |
| Serial Traceability | Individual serial numbers with forward and backward genealogy across production steps | High | Available |
| Quality Control | Inspection plans, recorded inspections, quarantine and release gates on production completion | High | Available |
| Production Costing | Material, labour and overhead accumulated per order and settled against standard | High | Available |
| Material Planning | Requirement explosion against demand and on-hand, shortage list | Medium | Available |
| Job Work / Subcontracting | Material issued to a vendor stays your stock; challan and ITC-04 tracking | Medium | Available |
| Inventory Valuation | FIFO valuation layers and weighted average, per item, on one ledger | High | Available |
| Purchase to Payment | PO, GRN, three-way match, vendor bills and payments | High | Available |
Rebota is used across a wide revenue range, and the honest answer differs by band. This is what it replaces outright, what it replaces with gaps you should plan around, and where you would be better served elsewhere today.
| Annual turnover | Verdict | What that means in practice |
|---|---|---|
| ₹1 lakh – ₹1 crore | Replaces | Replaces Tally and spreadsheets outright. You get batch and serial traceability, real production orders and GST compliance that a Tally-plus-Excel setup cannot give you at any price. |
| ₹1 – 10 crore | Replaces | Replaces Tally and Odoo Community outright for discrete manufacturing. Routings, shop-floor capture, OEE, QC gates and order settlement are all live and reachable. |
| ₹10 – 100 crore | Replaces with gaps | Usable as your system of record, but plan around two absences: there is no finite capacity scheduling, so the production plan stays in a planner's spreadsheet, and there is no multi-plant consolidation. |
| ₹100 crore and above | Not yet | Not yet. At this size you need capacity planning, PLM and multi-plant as table stakes, and none of the three exists. SAP or a tier-one system is the right answer today. |
What is built and enforced in the product today, by jurisdiction. Anything not listed here is not claimed.
To be direct: India is the only jurisdiction whose statutory filing is actually built. Other countries are supported as reference data — you can trade, invoice and report in their currency and financial year, but there is no local e-invoicing, no local tax return, and no local payroll. Do not buy Rebota today to file in another country.
| Alternative | Stay with it when | Move to Rebota when |
|---|---|---|
| Tally | Your accountant lives in it, you have no production floor to track, and inventory is a stock register rather than a process. | You need to know which lot went into which unit, or you need a production order to be more than a journal entry. |
| SAP | You need finite capacity scheduling, PLM, or process manufacturing with recipes and potency — all genuinely absent here. | You are paying enterprise licences and a consultant retainer to use perhaps a tenth of it. |
| Odoo | You have in-house Python capability and want to own and extend the codebase. | You want Indian statutory compliance working on day one rather than assembled from community modules. |
| Excel and WhatsApp | One product, one operator, one customer. | The moment two people need the same number at the same time, or an auditor asks who changed it. |
If one of these is core to how you run, Rebota is the wrong choice today and we would rather you knew now than in month three.
| Not built | Who actually needs it |
|---|---|
| Finite capacity scheduling and MPS | Anyone whose constraint is machine hours rather than material. There is no capacity model, so the schedule stays in a planner's spreadsheet. |
| PLM — engineering change control, revisions, approvals | Regulated or design-heavy manufacturers who must prove which drawing revision a batch was built to. |
| Process manufacturing — recipes, co-products, by-products, potency | Chemicals, pharma, food and any continuous process. Rebota is discrete-only today; a batch that yields two saleable outputs cannot be modelled. |
| Multi-plant consolidation | Groups running several factories that need transfer pricing between them and one consolidated view. |
No sign-up, no email. These run entirely in your browser.
