1. Scenario Overview
Order management follows the life of a transaction. Settlement and revenue sharing is about how the money is split. A plan purchase, a renewal, and a top-up each create an order, with a status such as pending payment, paid, completed, refunded, or closed. The order is tied to payment, to plan provisioning, and to resuming a SIM. A successful payment updates the status and provisions the plan, so payment is when the service starts.
The job here is the record and the status. An end user can look up an order, ask for a refund, or ask for an invoice. The business can count and export orders by user, time, or type. Settlement and revenue share is how that money is then split with a channel. Together they are the transaction and the funds path.
2. Core capabilities
Status from open to done
Created, pending payment, paid, completed. A refund can be partial or full. An order closes on a payment timeout or when the user cancels. Each plan purchase, renewal, and top-up is its own order, with an order number you can look up. Statuses include pending payment, paid, refunded, closed, and payment timed out.
What a successful payment does
The payment callback updates the order, provisions the plan onto the SIM, and resumes a SIM that was stopped for non-payment. It is wired to payment integration, plan subscription, and suspend and resume. The callback has to be idempotent, so a repeated notice does not provision the plan twice. Payment is when the service starts.
What the end user can do
Look up orders by time and status, request a refund, and request an invoice. A refund follows the rules — for example, unused, and not yet provisioned. The money goes back the way it was paid. Invoices can use an e-invoice service, including a VAT general invoice and a VAT special invoice.
What the business can count
Slice by user, time, order type, or payment channel. Search by order number, user, time, status, or channel. Export a daily, weekly, or monthly report for operations, reconciliation, and audit.
3. How an order moves
4. Orders and revenue sharing
They answer different questions:
| Dimension | Order management | Settlement and revenue sharing |
|---|---|---|
| The question | What was bought | How the revenue is split |
| What it does | The order record, status changes, refunds, and invoices | Share calculation, fund allocation, and channel settlement |
| What it is built on | The transaction: a plan purchase, a renewal, or a top-up | Those order records, allocated to agents and distributors |
| What people ask for | An order they can trace, and a clear refund and invoice path | Share rules they can read, and a settlement they can trace |
Use both. The order is the transaction. Settlement and revenue sharing splits the money from that record. The sale and the funds each have a trail.
5. Where teams use it
- A plan purchase: The user picks a plan and pays. The plan is provisioned. The order holds the whole path, and the service starts at payment.
- A renewal: When the plan expires, a successful payment extends it. The order is the record of that renewal.
- A refund and an invoice: Unused service can be refunded back to the original payment method. A paid order can request an e-invoice, either a general VAT invoice or a special VAT invoice.
6. What a traceable order changes
Status is something you can follow. Refunds and invoices have a defined path. Business statistics are what operations, reconciliation, and audit actually use. With settlement and revenue sharing, the sale and the money each close on a record.
7. How to put it in place
Write the status changes first, including the exceptions, such as closing an order when payment times out. Refunds go back through the payment channel, so set the refund rules before the first request. Invoices can use an e-invoice service. The link from order to payment, plan, and SIM resume has to be idempotent. SimtoLink can help configure the order flow and the refund rules.