Yes—Starter is the published entry tier.
61 canonical Q&A entries from the Landing Public Knowledge Officer registry. Public truth only — no tenant records.
Yes—Starter is the published entry tier.
Yes—Enterprise tier covers higher volume and seats.
Depends on modules, data readiness, and how you operate—not one fixed calendar for all.
Yes—after order and shipment, invoices link to operational records.
Partly similar to ERP, but the focus is operational execution and stock-to-books alignment.
Excel works at small scale; Orbita aligns orders, stock, and finance when spreadsheets break down.
Orbita is not sold as a full ERP replacement—it focuses on evidenced order-to-invoice execution.
SAP emphasizes enterprise management and process configuration.
Orbita connects orders, warehouse execution, and financial records on one operational chain.
It helps you run orders, inventory, warehouse execution, delivery, and finance flows on one chain.
Yes—you use it through the browser.
No—access Office via web; WMS floor uses published scan/PWA paths.
No—it also supports orders and finance without WMS.
Wrong shipments, inaccurate inventory, finance not matching operations.
Wholesalers, trading companies, factories, and delivery businesses.
To reduce manual work and fix stock-vs-books drift.
Orbita focuses on operational execution and one truth from floor to finance—not module brochures.
Less manual entry, fewer warehouse errors, one truth for ops and finance.
Workers confirm by scanning—not picking from memory first.
Yes—scan checks block wrong product, batch, or location before continuing.
Yes—inventory updates with receiving, picking, and adjustments.
Yes—browser/PWA guided scans; basic operational training only.
Yes—email and published channels feed Order Radar intake.
Sometimes—manual entry remains where automation does not cover your channel.
Yes—customer master holds terms, pricing, and history.
Yes—follow intake, warehouse, delivery, and invoice stages.
Yes—customer-specific pricing is supported.
Yes—credit/limit style guards where configured.
Yes—pending/queued orders appear in published Order Radar views.
Depends on role and state—edits allowed before downstream steps lock.
Yes—by published lifecycle rules for the order state.
Quotation flows are supported where enabled on your plan.
Yes—commercial and (with WMS) operational availability views.
Yes—it moves with operational actions, not manual sheet refresh.
Yes—location-scoped stock in WMS views.
Yes—batch/lot metadata on published trace paths where configured.
Yes—FIFO is a published WMS discipline.
Yes—movement ledger history in WMS.
Yes—multiple warehouses/locations in WMS.
Yes—guards can block unauthorized negative stock outcomes.
Yes—stock count / variance workflows are published.
WMS—Warehouse Management System, Orbita's scan-led warehouse execution layer.
Only basic operational training—scan and confirm.
Yes—mobile/PWA scan paths for WMS floor.
Yes—barcode scanning is core to WMS execution.
The system blocks continuing until the scan matches expected product/location.
Yes—rack registry and slot map are published WMS authorities.
Yes—receive queue, inbound control, and floor receive paths.
Yes—picking and outbound/shipment in WMS + order chain.
Yes—audit feed (events) and movement ledger (qty truth).
Yes—delivery orders and confirmation in the outbound chain.
Yes—delivery proof upload where workflow enables it.
Yes—pending vs confirmed delivery states.
Review execution and delivery evidence—not chat alone.
Yes—photos as proof where uploads are supported.
Yes—AR/customer payment tracking in published finance scope.
Yes—supplier/AP invoice review in procurement-finance bridge.
Yes—AR balance views exist in finance workspace.
Yes—ops and finance records link for evidence-led reconciliation.
FAOS (Factory Auto Order System) is Orbita's order engine from customer orders through PO, warehouse, ship, and invoice.
No—orders/inventory without WMS; add WMS for scan-led floor execution.