# Getting started

## Getting started

Bulletins highlight software and hardware changes that affect your sites.

Use them to understand what changed, why it matters, and what action to take.

Bulletins act as a single source of truth for customer-impacting updates, requirements, and limitations.

{% hint style="info" %}
Use Bulletins first when you need current guidance on a new change.
{% endhint %}

### What you will find in a bulletin

* A summary of the change.
* The customer or site impact.
* Any required action, timing, or limits.

### When to use Bulletins

* Before a software or hardware rollout.
* When validating whether a change affects your sites.
* When preparing support or operations teams.

### How to use this section

{% stepper %}
{% step %}

### Open the relevant bulletin

Choose the bulletin that matches the feature, issue, or operational change.
{% endstep %}

{% step %}

### Review the impact

Confirm who is affected, what changes, and whether action is required.
{% endstep %}

{% step %}

### Complete the next step

Apply the guidance, then share the bulletin with the right teams.
{% endstep %}
{% endstepper %}

### Start here

* [Penny Elimination](/petroleum-docs/petro-and-c-store/commander-and-integrated-pos/bulletins/penny-elimination.md)
* [Prompts for Loyalty PCATS](/petroleum-docs/petro-and-c-store/commander-and-integrated-pos/bulletins/prompts-for-loyalty-pcats.md)
* [Avoiding POS Downtime Due To Auto Upgrade Failure](/petroleum-docs/petro-and-c-store/commander-and-integrated-pos/bulletins/avoiding-pos-downtime-due-to-auto-upgrade-failure.md)

### Next step

Open the latest relevant bulletin before you change site software, hardware, or payment workflows.


---

# Agent Instructions: 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:

```
GET https://docs.verifone.com/petroleum-docs/getting-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.