How does Nordix BIOS handle order intake across channels?
A long-standing B2B customer fires an order on WhatsApp. A new buyer sends a PDF by email. A retail chain pushes EDI. BIOS reads all three, normalises them into the ERP order format, checks credit and stock, and confirms ETA in the channel the customer sent on. The sales desk sees only the orders that need human attention — exceptions, new accounts, contract renegotiations.
For mature accounts, ordering becomes conversational: "Same as last month plus 20 percent on SKU 4471." BIOS pulls the order history, applies the change, asks for the PO number and confirms. The buyer never opens a portal.
We used to have three full-time order entry clerks. BIOS handles 87 percent of orders end-to-end across WhatsApp and email, and the team finally has time to fix the systems that were broken.
Traceability, supplier follow-up and incident escalation
Lot and batch traceability is one of the boring questions BIOS answers fastest. A customer asks where lot 240817-A is in the system; BIOS reads the WMS and the production log, answers with the production date, the originating raw materials, the certificate of analysis and the dispatch records — in chat, in seconds.
Supplier follow-up runs the same way. Overdue purchase orders go to the supplier on WhatsApp or email, BIOS asks for a revised ETA, escalates if the supplier misses the response window, and notifies the buyer when the answer changes. The purchasing manager sees a daily exception report instead of chasing the inbox.
Quality incidents and customer complaints are routed by severity. A non-conformance from a key account pings the plant manager directly with the order, the lot, the photos and the customer history attached. BIOS holds the customer thread warm with status updates while the team investigates.
Daily inventory, throughput and order-aging reports push to the BI tool the operation already uses — Looker, Metabase, Power BI or Google Sheets — at the schedule the head of operations sets.
A typical day at a distributor with Nordix BIOS
A typical day at a distributor with Nordix BIOS
From the 6am EDI batch to the evening exception report, BIOS keeps the operation moving with a smaller back office.
~PT12H
- 1
6:00 — EDI batch
Overnight EDI orders from chain customers land. BIOS normalises into the ERP, runs credit and stock checks, confirms ETA back over EDI.
- 2
8:30 — WhatsApp orders
Regional B2B customers fire reorders on WhatsApp. BIOS reads each thread, applies the order, confirms in chat.
- 3
11:00 — batch trace request
A pharmacy distributor asks where lot 240817-A is. BIOS answers with production date, raw-material lots, CoA and dispatch — in chat.
- 4
14:00 — supplier follow-up
Three POs are overdue. BIOS pings each supplier, collects revised ETAs, updates the buyer's dashboard.
- 5
16:30 — quality incident
A non-conformance flag from a key account routes to the plant manager with the lot, the photos and the customer history attached.
- 6
18:00 — daily report
Inventory, throughput and order-aging report pushes to Power BI for the morning ops review.
See Conversational operations, Scheduled task automation and the BIOS module.
Frequently asked questions
Which ERP and WMS systems does Nordix BIOS connect to?
Nordix BIOS integrates with SAP, Oracle NetSuite, Microsoft Dynamics, Sage, PHC, Primavera, Odoo and the major European and Brazilian ERP platforms. On the warehouse side BIOS connects to Manhattan, Infor, Körber, Mecalux and the open-source WMS leaders. For custom builds and legacy systems, BIOS uses the same screen automation it uses elsewhere in operations.
Can BIOS process EDI in production?
Yes. Nordix BIOS reads EDIFACT, X12 and the regional dialects through the EDI translator the operation already uses (or through a partner translator). Inbound orders land in the same queue as WhatsApp and email orders, normalised into a single internal order shape. Outbound order confirmations, ASN and invoicing all flow through the same EDI gateway.
How does batch and lot traceability work?
Nordix BIOS reads the WMS lot ledger, the production system batch records and the supplier raw-material lots, and joins them on request. When a customer or auditor asks where lot 240817-A is, BIOS returns the production date, the input materials, the certificate of analysis and the dispatch records in a single message. Recall scenarios use the same engine to identify and contact every affected customer.
How are quality incidents escalated?
Incidents are classified by severity at intake — customer complaint, internal non-conformance, supplier defect, recall — and routed to the right human owner. The plant manager, QA lead or supply manager sees the incident with the lot, the order, the customer history and the photos already attached. Nordix BIOS holds the customer thread warm with status updates while the team works the problem.
Which BI tools does BIOS push reports to?
Nordix BIOS pushes daily, weekly and ad-hoc reports to Looker, Metabase, Power BI, Tableau and Google Sheets through their native APIs. The head of operations defines what the report contains — inventory aging, order throughput, supplier OTIF, exception counts — and the schedule. BIOS also responds to ad-hoc questions in chat without producing a static report.
Does BIOS chase suppliers as well as customers?
Yes. Nordix BIOS runs the supplier side of the relationship the same way it runs the customer side. Overdue purchase orders get a WhatsApp or email message asking for a revised ETA. Missed response windows escalate to the buyer. New supplier prices and contract renewals trigger the supplier-facing playbook. The purchasing manager sees only the exceptions that need human judgement.
Move the back office out of the inbox.
See how Nordix BIOS unifies order intake, traceability, supplier follow-up and reporting across every channel.
Glass preview
Your first operating thread
Real chat · opens in WhatsApp