> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/supplyd-erp/settings/report-settings.md).
# Report Settings
Report Settings in Supply’d let you tailor how data is displayed and shared, making it easier to track performance, stay informed, and make better business decisions.
The **Report Settings** page in Supply’d allows you to customise how your business reports are generated and displayed. Here, you can set your preferred report formats, helping ensure your reports are clear, accurate, and aligned with how you track performance and make business decisions.
***
## Applying & Editing Report Settings
{% stepper %}
{% step %}
#### Go to Settings
Click on your company name in the top right and select **Settings**.
***
{% endstep %}
{% step %}
#### Select Report Settings
Scroll down and select **Report Settings** from the **Settings** menu.
The **Reports Settings** form will open.
***
{% endstep %}
{% step %}
#### Complete the Form
Complete the **Reports Settings** fields as follows:
**Sales Date Reference**
Select the date by which you want the sales report to be filtered - **Order**, **Delivery**, **Shipped** or **Completed Date**.
**Purchase Date Reference**
Select the date by which you want the purchase report to be filtered - **Order**, **Delivery**, **Shipped** or **Completed Date**.
**Product Identifier**
Select the product reference you want to appear on product-based reports - **SKU**, **Barcode** or **Carton Barcode**.
**Convert Carton Sales To Units**
Select whether or not products sold as cartons should be converted to units for reporting.
Recommended to set to "**Yes**" if you sell both by unit and carton.
***
{% endstep %}
{% step %}
#### Click Save
Click to apply your settings.
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.supplyd.co/supplyd-erp/settings/report-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
to apply your settings.