Use Cases
Real workflows that businesses build on Miridia, across demand planning, manufacturing, procurement, inventory, multi-branch operations and delivery.
Miridia Planner backtests a pool of classical statistical models and gradient boosted trees against your own order history, SKU by SKU, and picks a champion for each one. A champion only ships if it beats a naive benchmark, so a sophisticated model never wins on reputation alone.
Forecast value added is tracked at every layer: the statistical baseline, the planner adjustments on top of it, and the published consensus. If a planner is making the forecast worse, the number says so. Most planning tools never measure this, so nobody finds out.
A planner wants to know what a 10% increase on a hero SKU does to demand. Run an elasticity-based scenario against the current forecast, review the projected impact, and promote the scenario into the live plan once sales has signed off.
Each function reviews the same forecast and records its adjustment. Compare an external forecast from the sales team or a third party against the forecast the system produced. The published consensus recalculates reorder points and drives the MRP report.
A stockout is not low demand, and a one-off bulk order is not a trend. The layered demand model separates raw actuals from cleansed history, so a promotion or an outage does not teach the model the wrong lesson for the next twelve months.
A work order consumes raw materials and produces finished goods, and both sides post to the inventory ledger with cost-of-goods valuation. Compare the material you planned to consume against the material you actually consumed, so yield loss shows up as a number rather than a suspicion.
Define a bill of materials with component quantities, scrap factors, and production costs for labour and overhead. Miridia resolves component purchase prices from price history at any given date, so you can see how the assembled cost moved over a year rather than guessing at it.
Bills of materials carry revisions with effectivity dates. Change a formulation, and the costing for orders produced before the change still resolves against the version that was live at the time. This matters when a customer asks what was in a product six months ago.
The published forecast feeds MRP and reorder point recalculation, and the bill of materials explodes finished-goods demand into component demand. Raw material purchase orders follow from the production plan instead of from a spreadsheet somebody maintains by hand.
Assign more than one supplier per product, with lead times tracked per supplier. When a preferred supplier is slow or short, the alternative is already in the system with its own pricing and lead time, rather than known only to whoever does the buying.
Set reorder points and safety stock per product per location. When stock falls below the reorder point, Miridia raises purchase orders to the preferred supplier and groups them by supplier so you consolidate volume. Track the lifecycle from draft through confirmation to receipt.
A goods received note posts straight into the inventory ledger and updates costing automatically. Partial receipts are normal, not an exception to handle by hand, and the delivery note flows through to your accounting platform.
Somebody requests, somebody approves, and the approved requisition becomes a purchase order without a second data entry. The approval sits in the system, so the question of who authorised a spend has an answer that is not an email thread.
Delivery performance, fill rates, defect rates and spend are captured from purchase order history rather than from a survey. Build a workflow that alerts procurement when a supplier drops below the threshold you set, so the conversation happens before the shortage does.
Collect quotations against the same requirement and compare them side by side, for goods and for freight. Spend visibility across a supplier base is also the evidence you take into a negotiation for volume pricing.
Per-location inventory records track three quantities: on hand, reserved, and in transit. View a consolidated position across all locations or drill into one, with a complete movement audit trail behind every number.
On hand is not the same as available. Miridia reserves stock automatically when an order is taken, so the free quantity drops the moment the order lands rather than at pick time. Two channels cannot sell the same last unit inside a sync gap.
The ledger is append-only. Every increase and decrease is a row with a running balance, a unit cost, and a reference to the document that caused it, whether that is a purchase order, a transfer, or a work order. Nothing changes stock without leaving a row.
Move stock with a transfer order that tracks the in-transit quantity, so units are not counted twice while they sit on a truck. Inventory updates at both ends when the receiving site confirms.
Weighted average or FIFO, set per inventory record. Every movement carries its unit cost and the running average after it, so a margin question resolves against the ledger rather than against an estimate.
Run a cycle count and Miridia reports the variance against the recorded quantity, so a correction is a documented movement rather than a silent edit. Counts reported by a connected eCommerce or warehouse platform reconcile automatically against the right location.
From a purchase order receipt, Miridia lists the customers who most probably received that stock. From a customer shipment, it lists the probable source receipts and their suppliers. This is an inference over the ledger on a first-in-first-out basis, and the report says so on its face. It is not lot tracking, and it does not identify a physical consignment.
A branch manager raises a transfer order request for the products and quantities they need. The fulfilling location reviews it, approves it, and dispatches the stock, which is tracked in transit until the branch receives it. Branches use the same transfer flow as everyone else, so there is no separate internal-order system to learn.
Create price lists and assign them to locations or delivery zones, with a priority you control deciding which list wins when several apply. When an order is placed, Miridia resolves the effective price and falls back to the default price history when no list applies. Every price change is tracked for audit.
Configure a master and sub-business hierarchy so every sub-business inherits the master catalogue, supplier list and pricing strategy. Use visibility controls to restrict items per location. A branch manages its own inventory and orders, and cannot alter the shared catalogue.
Sub-businesses keep independent transactional data while the master sees the consolidated position. The question of how the group performed does not require somebody to collect a file from each branch on the last day of the month.
An operations manager enables the stock watcher and the order data-quality agents. Overnight an integration starts writing orders with malformed delivery addresses. By morning there is a warning in the findings inbox naming the affected orders, before a single customer called.
A finance director wants to know which suppliers caused the most stockouts at the distribution centre over six months. They ask directly instead of queuing behind an analyst. AI Studio generates the query, returns a chart, and summarises what it found, grounded in live data and read-only by construction.
Agents run on a schedule and deduplicate what they raise, so the same issue does not arrive as forty notifications. An agent that has learned a cheap recurring check keeps running it for almost nothing, which is what makes around-the-clock monitoring affordable.
An event-driven workflow engine connects to n8n, Power Automate, Zapier and webhooks, over a full REST API. Most software asks you to work the way it prefers. This is the path for the rule that is specific to how you operate, and it does not need a vendor release to exist.
A pluggable pipeline syncs the relevant tables into your own PostgreSQL or BigQuery instance on a schedule, so Power BI and your downstream systems read reconciled order and inventory data. The data belongs to you, which means analytics is not a place you can be locked in.
Generate reports on customer or order data through workflows or the API, save them to the dashboard, and schedule them to run and distribute on their own.
Receive a Telegram or Slack notification the moment a return comes in, or skip the notification and build the workflow that handles it: auto-approve under a value threshold, generate the return label, and tell the warehouse.
If the platform you run is not on the integration list, our consultants build the connector. Where it is reusable for other customers, we build it at no additional cost rather than quoting an integration project.
Aggregate quotations from multiple logistics vendors and compare rates for each shipment. Combined with workflow rules, carrier selection automates on cost thresholds, delivery speed, or geographic zone.
Use a specific local company for same-day delivery within your city and a different provider for long distance. Split carriers between national and international to cut cost, or to give a better delivery experience depending on where the customer is.
Ship pallets and containers between stores, plants and warehouses, with the same tracking and cost comparison as a parcel. Most fulfilment software stops at the parcel, which leaves the freight half of a retail or manufacturing operation outside the system.
Hand a parcel, pallet or container to a different logistics partner mid-journey. Miridia keeps the tracking data across each transfer and compares the cost of each forwarding option.
ZPL printing to Zebra hardware with custom templates, on site or from the cloud. The common setup is on-site printing at 300 DPI, wired into the fulfilment workflow so the label prints when the workflow says it should.
Smaller logistics companies join the network rather than being locked out of it. Customers get more delivery options and better regional rates, and the carriers get delivery leads from retailers already on the platform.
A food manufacturer moves frozen and chilled product through contractors with no direct telematics. Miridia captures cold-chain cost data on transfers, integrates with carrier telematics where it is available, and raises a workflow exception on a temperature breach. The audit trail supports an FSSC 22000 review.
Inventory movement trails, bill of materials versioning and work order records support FSSC 22000, HACCP and ISO reviews. The evidence is a query rather than a week of assembling documents.
Manage HS codes on products and build workflows that produce the documentation an international shipment needs. Tariff calculation and customs paperwork run from the same data as the shipment.
Multi-jurisdiction tax models cover VAT, sales tax and regional variants, so selling into a second country is a configuration rather than a second system.
Moving from WooCommerce to Shopify. Miridia syncs customer and product data across both platforms, which can save hundreds of hours and keeps you out of a vendor lock-in you did not choose.
Switching from QuickBooks to Xero is usually painful. Our consultants have done these migrations and can move customer data, product data, and in some cases invoices and ledgers.
Onboarding migrates your existing data, and Miridia can run in parallel with the system you are leaving. You do not have to choose between a clean cutover and keeping the record of what happened last year.
MAKE. MOVE. MEASURE.
Our consulting team can help build custom workflows for your specific requirements.