Operational data model
Customers, vendors, items, SKUs, orders, POs, shipments, invoices, bins, packages, tasks, and documents live in one operating model.
Platform
The operating platform underneath complex warehouse businesses.
ORCA connects the work that usually gets split across WMS screens, order tools, native apps, print stations, spreadsheets, shipping portals, accounting systems, custom scripts, reports, and support tickets.
Orders
Inventory
Warehouse
Finance
Integrations
Platform spine
One operational model, many workflows.
ORCA works because the important business objects are connected. Orders, inventory, shipments, packages, purchase orders, invoices, payments, documents, tasks, and integrations share context instead of living in separate tools.
Workflow engine
Status, queue, rule, hold, approval, and exception flows keep work moving through the business with clear ownership.
Integration fabric
Marketplace, shipping, ERP, accounting, payment, EDI, vendor, and custom systems connect around the same operational truth.
Automation layer
Jobs, event hooks, document generation, confirmations, audits, and structured support workflows reduce manual follow-up.
Document and label system
Packing slips, carton labels, SSCCs, BOLs, invoices, customer documents, and partner outputs are generated from operational state.
Controls and permissions
Roles, tenant settings, approvals, audit trails, status transitions, and review queues keep sensitive work governed.
Reporting and decision layer
Warehouse aging, sales, forecast, pick performance, payments, collections, and exception reports draw from the same work records.
Support and delivery system
Requests, threads, tasks, tenant context, engineering notes, structured routing, and closeout records stay connected.
Built on the platform
The rest of ORCA works because the foundation is shared.
Warehouse execution, native apps, integrations, adaptable workflows, finance, support, and reporting should not be separate products stitched together after the fact. They should be different views of the same operating system.
Warehouse Execution
Uses the shared model for shipments, packages, bins, labels, operators, queue states, packer rules, and exception recovery.
Floor workIntegrations
Connects marketplaces, carriers, payments, EDI, accounting, vendor software, and custom APIs into live operational records.
External systemsAdaptable Workflows
Extends existing workflows with tenant rules, custom logic, engineering delivery, and support context without creating side systems.
Business fitApps and Workstations
Brings camera scanning, native notifications, geofence reminders, desktop printing, and tenant-aware sessions into the same operating layer.
Native accessSecurity And Governance
Supports access control, least-privilege integration handling, privacy requirements, audit context, and operational data discipline.
Trust layerWhat the platform connects
ORCA is not just warehouse execution. It is the system around it.
The warehouse is where the work becomes physical, but the platform has to understand the commercial, financial, production, and integration context around that work.
Orders and customers
Sales orders, customer rules, holds, shipping methods, portals, confirmations, and order status visibility.
Inventory and purchasing
On hand, allocated, available, bin-level stock, POs, inbound shipments, receipts, replenishment, and valuation.
Warehouse execution
Receiving, pick, pack, ship, freight, labels, manifests, scanner flows, package records, and exception queues.
Native app access
iOS floor workflows, Mac and Windows desktop stations, camera barcode scanning, notifications, print stations, and geofence reminders.
Production and assembly
BOMs, work orders, production queues, router steps, machine status, build handoffs, and component movement.
Billing and payments
Invoices, deposits, prepayments, payment gateways, invoice aging, shipping reconciliation, and finance exceptions.
Reporting and decisions
Warehouse aging, pick performance, shipped volume, sales, inventory, forecast, collections, and operational exceptions.
Platform proof
Every workflow can see the same business reality.
A shipment is not just a shipment. It can affect inventory, packages, carrier labels, customer notifications, invoices, payment capture, accounting sync, reporting, and support follow-up. ORCA is built so those pieces can move together.
- Warehouse actions can trigger documents, confirmations, invoices, and integrations
- Finance can see operational state instead of chasing warehouse updates
- Support can work from thread, task, tenant, order, and route context
- Custom workflows extend the platform instead of becoming side systems
Platform services
The foundation is made of operational services, not just modules.
Modules matter, but the real leverage comes from the services underneath them: rules, state, jobs, documents, native app hooks, integrations, audit trails, reporting, and support context.
Workflow state
Statuses, queues, holds, approvals, ownership, review points, and exception paths stay attached to the records being worked.
Rules and tenant logic
Customer rules, carrier rules, packer configuration, document requirements, billing behavior, and tenant-specific automation.
Jobs and events
Scheduled work, event hooks, confirmations, imports, exports, retries, alerts, and background automation keep follow-up moving.
Documents and output
Labels, BOLs, packing slips, invoices, reports, partner files, EDI documents, emails, local desktop printing, and operational exports.
Audit and visibility
Reports, task history, integration requests, shipment state, inventory movement, user action, and exception trails remain inspectable.
Support delivery
Request triage, task routing, context gathering, run summaries, QA review, response drafting, and workflow delivery support.
Built to fit operations
Powerful out of the box, adaptable where the business is different.
The platform starts with real WMS and operations capability, then gives the business room to adapt workflows that are strategic, unusual, or too costly to keep manual.