01 — The problem
Why orders get lost between teams
Orders often arrive through several routes: a webshop, email, phone and sales reps. Each lands somewhere different, and someone retypes them into the system that handles fulfillment. Status questions from customers mean checking three places.
The real trouble is exceptions. A large discount needs approval, a customer is over their credit limit, one line is backordered and ships separately, a return arrives without a reference. Spreadsheets can't enforce those rules, and generic order management software may not model them the way your business actually works.
02 — What to build
Key objects in a custom order management system
Orders with customer, channel, order date, requested delivery date and owner.
Order lines with product, quantity, price, discount and line-level status.
Approval rules for discounts above a threshold or customers on credit hold.
Fulfillment tracking
picked, packed, shipped, partially shipped, backordered.
Returns with reason codes, condition and refund or replacement decision.
Customer-facing status so service reps can answer "where is my order?" in one lookup.
Roles
sales enters orders, finance approves credit holds, fulfillment updates status, service sees everything read-only.
The warehouse side can live in its own warehouse management app if your floor team needs more detail.
03 — How to build it
How to plan and build it in Henosia
Create a private project
Nothing reaches customers or colleagues until you publish.
Add representative mock data
anonymized orders, order lines, customers and products as CSV exports.
Connect a database so orders and statuses are stored in proper tables.
Work through Plan mode
The agent asks clarifying questions about statuses and approvals and proposes a plan before building.
Build a first version, then test the hard cases: partial shipment, credit hold, return without a reference.
Refine with prompts and publish to each team with the right permissions.
Plan an internal order management app for B2B orders from email, phone and sales reps.
Use orders.csv, order_lines.csv, customers.csv and products.csv as mock data.
Discounts above a customer's agreed terms need sales manager approval; customers over their credit limit go on hold for finance.
Lines can ship separately; show backordered lines with expected dates.
Give customer service a read-only order lookup by customer name or order number.Paste it into a private Henosia project in Plan mode. The agent asks questions and proposes a plan first.
04 — Before you go live
Define order statuses before going live
In a Henosia webinar, Danish e-commerce company 4tal described getting data definitions aligned across teams before automating anything. For orders, that means agreeing what "confirmed," "shipped" and "complete" mean, and which system owns each status.
Then settle the practical points:
- Data owner for order and customer records.
- Integrations: Henosia can work with data connections and API-based data; scope each one per system, data direction and access level. More point-and-click connector interfaces are on Henosia's roadmap.
- Read vs. write: start read-only toward other systems until the app is tested.
- Publishing approval and who maintains the rules afterward.
Start a private project in Henosia with a sample of last month's orders and plan your first version.
Start a private project05 — FAQ
Frequently asked questions
What is the difference between an order management app and an order management system?
An order management system is usually a broad platform covering orders across all channels. A custom order management app can focus on the parts your team struggles with, like approvals, backorders or returns, and follow your exact rules. You can start narrow and extend it with new prompts.
Do I need a developer to build order management software?
Not for a first version. In Henosia you describe the workflow in Plan mode and build from mock data without writing code yourself. For production, involve IT or a developer to scope integrations, set access rules and review how the app writes to other systems.
Can customers track orders in the app?
Henosia focuses on business apps with controlled access. You can build a customer-facing order tracking app as a portal for your own customers, but decide carefully which data they see and how they log in. Many teams start with an internal lookup for customer service.
How is order and customer data protected?
Projects begin as private sandboxes. Published apps can be limited to your company email domain, specific users or IP ranges, and IT gets an overview of apps, builders and access. Confirm your specific requirements for customer data with your IT team and Henosia before going live.