> ## Documentation Index
> Fetch the complete documentation index at: https://support.parker.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Orders, bookings, and approvals

> Raise an order, book a visit, or ask for a sign-off from the field. Parker creates the record when you confirm; your Salesforce limits still apply.

Orders, bookings, and sign-offs from the field. Describe what you need, send a photo of the shelf or the part, and Parker drafts the record. It saves when you confirm, as you, so your own permissions, discount limits, and approval steps in Salesforce still decide what happens next.

## Before you begin

* [Get the Parker app](https://support.parker.work/mobile/parker-app.md#get-the-app).
* Your Salesforce login can create the record, such as an order, an appointment, or a quote.

## Raise an order or a booking

**1. Say what you need**

"Priya at Elm Pharmacy wants her usual paracetamol order, down to the last two packs." Or send a photo of the shelf with that line. For a booking: "Book a return visit at 9 Quarry Rise, Thursday morning, no access today, card through the door."

**2. Check what Parker found**

Parker finds the account, the product or asset, and anything it can reuse, such as the last order. If more than one could match, it asks.

**3. Answer anything missing**

Quantities, dates, and choices arrive as questions with buttons. Records you've used before are offered first.

**4. Confirm**

Parker shows the order or booking as a card. Tap **Confirm**. Parker creates it as you and replies with the number.

> [!NOTE]
>
> **Nothing is saved until you confirm.**
>
> Before Parker creates or changes a Salesforce record, it shows the change field by field. Nothing is written until you select **Confirm**. In the Parker app the card offers **Confirm**, **Edit**, and **Cancel**. In the web app it offers **Confirm** and **Reject**.
>
> See [How Parker acts on your behalf](https://support.parker.work/get-started/how-parker-acts.md).

## Approvals and limits

Your rules hold, even in the Parker app.

| What you ask for | What happens |
| - | - |
| A discount, variation, or value within your limit | Parker shows the change and saves it when you confirm. |
| Something over your limit, or outside your authority | Salesforce refuses the save. Parker quotes your org's own message and tells you what's needed, such as a manager's approval. |
| A record your org routes for approval | Parker creates the record. If your Salesforce is set up to submit records like it for approval automatically, that happens as it would for any record created through the API. If approval has to be submitted by hand, it still does: Parker never submits a record for approval. |

Parker submits nothing for approval, doesn't know whether a record is awaiting approval unless you ask it to read the record, and can't work around a validation rule. If a save is refused, it explains why and asks for what's missing. See [When Salesforce says no](https://support.parker.work/mobile/when-salesforce-says-no.md).

## Plan the day

Ask for tomorrow's route and Parker puts your stops in the best order, with the time for each leg: "Plan Thursday: start from home, Fremantle, Joondalup, Midland, finish by 4." See [Find records near a place](https://support.parker.work/maps/overview.md).

## Examples

| You send | What's created |
| - | - |
| A shelf photo: "Customer wants 4 of these. Do we have them?" | Nothing yet. Parker reads the product and answers from stock records you can see, then offers to raise the order. |
| "Kestrel Packaging want 15% off quote Q-10422." | A change to the quote, if 15% is within your limit. If not, Salesforce refuses and Parker tells you what's needed. |
| "No access at 9 Quarry Rise, calling card left. Rebook for Thursday." | A note on the job and a new appointment, each on its own card. |
| By voice: "New account, The Crown on Bridge Street, needs a credit check before first order." | A new account, and whatever your org creates next, such as a credit-check task from a flow. |

## What Parker doesn't do

* **Check stock in a system you haven't connected.** Parker reads what's in Salesforce. If your stock lives elsewhere, ask your admin whether it's connected.
* **Approve anything.** Approval stays with the people and processes your Salesforce defines.
* **Create records you can't create in Salesforce.** Parker runs as you, so your permissions and validation rules decide.

## Still need help?

Check [Troubleshooting](https://support.parker.work/reference/troubleshooting.md) for the exact message you see. If a setting is admin-only, ask your Parker admin. For anything else, [contact support](https://support.parker.work/reference/contact-support.md).

## Related

> [card] [Create and update records](https://support.parker.work/chat/updating-records.md)
>
> Any record, in a sentence.

> [card] [Check a status](https://support.parker.work/mobile/check-a-status.md)
>
> Stock, proposals, and account stops, before you commit.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.