Order to delivery, returns to restock — one traceable flow.
In retail and e-commerce the volume is the problem. A single order is easy; a hundred simultaneous orders across several channels, each with its own status, each capable of becoming a return, is where the process breaks down. Tenderely BPM connects the order, the stock, the fulfilment steps and the return into one structured record without code, so the team always knows what is waiting, what is moving and what has gone wrong.
What does an e-commerce or retail operation repeat every day?
01
Receiving and logging orders
Orders arrive from a website, a marketplace and a physical counter at the same time. Without a common record each channel is a separate queue and the total picture is invisible.
02
Picking, packing and dispatch
Someone has to pull the right items, confirm quantities, pack and hand to the carrier. Each handoff is a point where errors accumulate and accountability disappears.
03
Stock movements
Every sale reduces a quantity; every supplier delivery increases it; every return changes it again. When these movements are not in one place, the stated stock level and the real stock level drift apart.
04
Returns and exchanges
A returned item needs to be accepted, inspected, restocked or discarded, and the customer credited or replaced. Each of those decisions is a step, and skipping one creates a liability.
05
Supplier purchases and replenishment
Running low on a product triggers a purchase request, a quote comparison and an approval before a supplier order is placed. Done informally, overstocking and stockouts alternate.
06
Campaign and margin tracking
A discount campaign changes the effective margin on every item it touches. If the numbers are not visible during the campaign, the damage is only discovered at month-end.
Where does this break down today?
Channel orders never meet
The website orders are in one tool, the marketplace in another and the counter sales in a notebook. Nobody has a single view of what is pending, what is packed and what is late.
Stock levels are always a guess
Sales reduce stock, returns bring items back, supplier deliveries add more — but each happens in a different system or spreadsheet, so the live number is unreliable until someone physically counts.
Returns have no defined process
Whether a return is accepted, what condition the item is in, whether it goes back to shelf or gets written off — these decisions are made differently each time, and the customer does not always get the same answer.
Margin erodes silently
Discounts, shipping costs, supplier price changes and exchange rate movements each chip away at the margin. If nobody is watching the numbers in one place, the full picture only appears when profit does not.
What changes with Tenderely BPM
01
Every order is a structured record
Channel, items, quantities, customer, status and assigned team member sit in one record from the moment an order is placed. Nothing lives only in someone's inbox or messaging app.
02
Fulfilment is a tracked sequence
Pick, pack, dispatch and delivery confirmation are steps in a flow. Each step records who completed it and when, so delays have a name and a timestamp rather than a mystery.
03
Returns follow a consistent path
Inspection, restock or write-off decision, and customer credit or replacement are steps that cannot be skipped. The same process runs every time, regardless of who handles the return.
04
Approval steps enforce themselves
Supplier purchase approvals, discount authorisations and write-off decisions are configured as conditional steps without code, so the rule is inside the flow rather than in a policy document someone has to remember.
05
Mobile for the warehouse floor
Tenderely BPM runs in the iOS and Android apps, so a warehouse team member confirms a pick or flags a discrepancy from their phone without returning to a desk.
06
The numbers are simply there
Pending orders, stock on hand, open returns, supplier deliveries due and campaign margins sit on a dashboard that is current without anyone compiling a report.
FAQ
Can we handle multiple sales channels in one place?
+
Yes. Orders from any channel can be opened as records in the same system, assigned a channel label and filtered or reported by channel. The team works from one list rather than switching between tools.
Can customers submit return requests themselves?
+
Yes. A public form can be published as a link or embedded in your website or order confirmation email. A customer fills in their order details and the reason for return, and the record opens directly in your return flow — no account required from the customer.
How does the approval work for discounts or write-offs?
+
Conditional branching means the flow can require a manager approval only when the discount exceeds a threshold, or only when an item is being written off rather than restocked. The rule is configured without code, and an exception cannot be processed without being recorded.
Who can see what inside the system?
+
Unit-, role- and field-level permissions determine access. A warehouse operative can see and act on fulfilment steps without seeing cost or margin fields; a buyer can manage supplier purchases without seeing customer data. Each role sees exactly what it needs.
Is there a ready-made setup we can start from?
+
Yes. The E-Commerce and Retail package installs with forms, flows and a dashboard already in place. You adjust each form to match your products, channels and team, then publish. The package is a starting point, not a constraint — you can extend or change any part of it without code.