Credits are Eofferix internal processing units. The service uses them when it receives a source, parses elements, applies transformation rules, processes images, builds the result, and so on.
Where to Check Balance and Package
The current balance is shown in the top bar. The full plan details, storage, template limits, and concurrent run limits are available in Billing.
What Run Cost Consists Of
Before a run, Eofferix calculates an estimate. When the run starts, the estimated amount is reserved; after completion, only the actual spent credits are charged. If some files are unavailable, skipped by conditions, or do not need processing, the unused reserve is not charged.
- Source elements. Cost depends on the source type and the number of elements that need to be parsed.
- Target result. Regular results may have one cost, while some target formats and applications may add export cost.
- Value transformations. Rules, structure changes, new nodes, and repeated-value collection add cost for elements that are exported.
- Images and files. Downloading, resizing, format conversion, and watermarking are counted by file or image and are charged only when the processing actually runs.
Simple Examples
For example, the cost may be:
- parsing 1 element = 1 credit
- 1 transformation = 1 credit
- downloading 1 file to the service = 5 credits
- resizing 1 image = 20 credits
- converting the format of 1 image = 20 credits
- adding a watermark to 1 image = 10 credits
| Scenario | Calculation | Total |
|---|---|---|
| 2,000 products without rules or images | 2,000 × 1 | 2,000 credits |
| 2,000 products, export conditions leave 1,500, and one price cleanup rule is added | 2,000 × 1 for base processing + 1,500 × 1 for the rule | 3,500 credits |
| 500 products and 500 images with preparation, resize, conversion, and watermarking | 500 × 1 for elements + 500 × (5 + 20 + 20 + 10) for images | 28,000 credits |
If Credits Are Not Enough
First check the run estimate: it shows which parts of the template create the main cost. Often it helps to disable unnecessary image processing, remove unused rules, apply export conditions, or skip unchanged files.
If credits are not enough, you can switch to a plan with a larger monthly package, use a dedicated compute server without a credit limit, or buy extra credits once.
If automation is enabled and the source has not changed, the interpretation template will not run again. If the source images have not changed, repeated image processing does not start and credits are not charged for it.
Important Notes
- Credits cover data processing. Storage, template count, unified catalog limits, and concurrent runs are separate plan limits.
- Extra credits do not change the plan and do not increase storage.
- The final cost may differ from the estimate if the actual run processes fewer elements or files.
- If rates change, use the current estimate before launch and the What credits are block in Billing as the source of truth.