> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/portal/store-settings.md).

# Store settings

Store settings control the overall storefront rather than an individual Product. Configure them before publishing products so that buyers know who they are purchasing from and how to get help.

### Settings to review

| Setting area                    | What it changes for buyers                             | What to decide                                                                  |
| ------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------- |
| Store name and description      | The identity and introduction shown on the storefront. | Explain what the store offers and who it is for.                                |
| Branding and imagery            | The visual presentation around products.               | Use accessible colours and images consistent with the main portal.              |
| Payment connection              | Which payment account receives transactions.           | Keep test and live connections clearly separated.                               |
| Currency and commercial display | How prices are presented where supported.              | Confirm the intended market, tax treatment and finance process.                 |
| Contact information             | Where buyers go with pre-sale or order questions.      | Use a monitored address or support route.                                       |
| Terms and privacy links         | The policies available before purchase.                | Keep wording current and suitable for the customers and jurisdictions involved. |

### Before switching to live payments

* Restrict access to payment and store configuration.
* Confirm the legal entity, public contact information and policy links.
* Complete the entire journey with the payment provider's supported test mode.
* Agree who handles failed payments, refunds, chargebacks and access corrections.
* Check that transactional emails and confirmation pages use the expected portal branding.

{% hint style="info" %}
Changing a storefront setting does not necessarily change the terms of an existing purchase. Keep a record of material commercial changes and when they took effect.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://synap.ac/docs/platform/portal/store-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.