Order Credits vs Processing Units
ClearSKY uses two separate credit pools across the order lifecycle: one for creating orders and producing coverage, and one for retrieving files.
Older ClearSKY docs may refer to processing units as processing credits. These terms refer to the same download-usage pool; the current term is processing units.
At a Glance
| Credit type | Used for | When consumed |
|---|---|---|
| Order credits (EUR) | Creating orders and producing coverage | Consumed at order creation |
| Processing units | Download processing and file retrieval | When running processing/download requests |
The Key Billing Rule
Order credits pay for the order itself. Processing units apply later, when you download outputs from that order.
Each order includes enough processing units to download the produced data once. Processing units mainly matter when you perform repeated downloads or additional export variants.
Typical Lifecycle
- Create an order -> order credits are deducted.
- Data is produced and becomes available.
- First full retrieval pass is covered by included processing units.
- Later re-downloads or extra processing/download runs consume additional processing units.
When Processing Units Become Important
Processing-unit usage typically increases when you:
- Download the same order output more than once.
- Export multiple output variants (for example different EPSG, resolution, or band selections).
- Re-run download processing in separate batches for operational reasons.
If included processing units are exhausted, additional units can be purchased. See Storage and extra requests.
Separate from Storage Retention
Processing units and storage duration are separate controls. Even with remaining processing units, expired storage can still make data unavailable for download.