Track cost per order in ZopNight Unit Economics. Connect your order stream through CSV upload or Push API, then rank cloud cost recommendations by their impact on cost per order.
This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 60 minutes. Before you start you will want: A ZopNight account on a plan that includes Unit Economics; A daily order count from your e-commerce platform or order pipeline; At least one cloud account connected.
The steps
- Define the metric.
- Pick the ingestion mode.
- Send the first batch.
- Validate the data.
- Rank recommendations.
- Share the dashboard.
Why this is safe to do today
The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.
If you want the fuller context behind this task, the FinOps guide covers where it fits, and the AWS EC2 scheduling page shows the same loop applied to a specific resource.
Getting started
Getting started is intentionally low-stakes:
- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.
Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
How granular can cost per order be?
The base metric is one cost per order value per day. Adding a dimension (channel, region, order type) splits it across that dimension. A typical setup tracks cost per order overall and cost per order for each top-three channel.
Does cost per order include payment processing fees?
No. ZopNight cost per order covers cloud infrastructure cost only. To include payment processing or other operational costs, push the additional cost stream as a custom cost source.