creekpos · Classic Desktop
Export safely to Excel, JSON and BI · Classic Desktop
This guide uses fictional training data. Available controls depend on your enabled features, plan and permissions.
Prepared against the tested 13 October 2026 build; check your deployed build before following a new control.
Who can use this
Authorized report reader / integration manager
Required tools
Export access for the selected source. Requires the appropriate enabled features and entitlement; this guide does not add plan inclusions.
Before you begin
If a control is absent, check role, branch, enabled features and entitlement. If an order or price changed, refresh and review again. Do not repeat an uncertain financial action with a new request.
Native sales reports and product lists offer CSV, Excel and JSON. Other native reports retain their own typed Excel options. Power BI refresh and provider pushes are separate authorized connections; exporting a file does not activate them.
Steps
- Open the native report or product list and choose the desired date/time range and filters first.
- Select Export and choose CSV, Excel or JSON where the human report offers them. The sales report records its start and exclusive end in structured exports.
- Open the saved file and verify identifiers, Arabic text, totals and the selected period. Text cells preserve leading zeroes and do not execute formula-like names.
- Imports, device files and scheduled integration contracts retain their own formats. Native file export is not a live Power BI or Zoho connection.
Check the result
Review the saved record and its audit/stock/payment state before continuing. A preview, queued request or accepted send is not proof of completed delivery or settlement.
Edition differences and limits
Native sales reports and product lists offer CSV, Excel and JSON. Other native reports retain their own typed Excel options. Power BI refresh and provider pushes are separate authorized connections; exporting a file does not activate them.