# Store Manager Workflow

The **Store Manager** workflow is for employees who oversee daily operations, supervise other staff, and need broader visibility into performance data. It builds on the Cashier workflow with extra reporting, user-account oversight, and PIN override authority.

## When you'd assign this workflow

For employees who:

* Supervise cashiers and sales reps.
* Need cross-register reporting and EOD summaries.
* Authorise discounts, voids, or returns that require manager approval (PIN override).
* Manage or review customer accounts.
* Don't need POS-only restrictions.

## How it differs from the Cashier workflow

| Capability                 | Cashier          | Store Manager     |
| -------------------------- | ---------------- | ----------------- |
| Place Order / POS          | ✅                | ✅                 |
| Catalog browse             | ✅                | ✅                 |
| Customer lookup / create   | ✅                | ✅                 |
| EOD reports                | ✅ (own register) | ✅ (all registers) |
| Reports dashboard          | Basic            | Full analytics    |
| PIN override authority     | ❌                | ✅                 |
| User-management visibility | ❌                | ✅ (read)          |

The exact split depends on how your subsidiary has set things up — these are typical defaults.

## Typical module structure

| Position | Module                 | Type               | Purpose                                        |
| -------- | ---------------------- | ------------------ | ---------------------------------------------- |
| 1        | **Dashboard**          | Dashboard          | Manager landing screen with KPI overview       |
| 2        | **Header Navigation**  | Header Navigation  | Top bar                                        |
| 3        | **Sidebar Navigation** | Sidebar Navigation | Sidebar with manager-specific sections         |
| 4        | **Place Order**        | Order Form         | Full POS transaction screen                    |
| 5        | **Pay Invoice**        | Order Form         | Invoice payment collection                     |
| 6        | **Reports**            | Page               | Sales and activity reporting                   |
| 7        | **EOD Reports**        | Page               | End-of-day reconciliation across all registers |
| 8        | **Customers List**     | Page               | Full customer directory                        |
| 9        | **Customer View**      | Page               | Single-customer detail and history             |
| 10       | **Catalog**            | Catalog            | Full product catalog                           |
| 11       | **Support**            | Page               | Support case management                        |

Positions 1, 2, and 3 are locked.

## PIN override

Store Managers are typically the people who can authorise sensitive actions across the floor — discount overrides, void approvals, and so on. Two pieces have to be in place:

1. **The component (or workflow) requires a PIN.** Configured in the Page Builder for per-component PIN, or on the workflow's Settings tab → PIN Settings → **Require PIN** for workflow-wide protection.
2. **The manager has a PIN set on their NetSuite record.** Set by your **NetSuite Admin** in the user's `custentity_brm_pincode` field (or the field your org has configured as the PIN Code Field).

For the full picture, see [PIN Override](/client-admin-guide/workflow-builder-overview/pin-override.md).

## Customise the workflow

Common customisations:

* **Add a curated reports page** — use a Page or Reports module to surface a dashboard tailored to what your store manager actually monitors.
* **Add a staff-schedule or notes page** — a Page module with custom HTML can host a static schedule, training notes, or escalation guide.
* **Drop modules they don't need** — if your managers don't process transactions, remove Place Order and Pay Invoice to keep the nav clean.

For the broader walkthrough see [Creating Custom Workflows](/client-admin-guide/workflow-builder-overview/creating-custom-workflows.md).

## Assign the workflow to users

In **User Management**, find the manager and edit their row to set Role = *Store Manager* and Entity Type = *Employee*. Save. They see the workflow on next login.

If they need to authorise PIN-protected actions, your NetSuite Admin also has to set their PIN on their NetSuite record. See [Managing PIN Codes](/netsuite-admin-guide/overview-3/pin-codes.md).

## Common issues

* **Manager's PIN isn't accepted** — confirm the PIN was saved on the right NetSuite field (default: `custentity_brm_pincode`). The Workflow Settings → PIN Settings → **PIN Code Field** dropdown must point at the same field.
* **Manager sees the cashier portal** — wrong role on their user record. Edit them in User Management.
* **Manager can't see all-register EOD** — that's a NetSuite-side configuration issue with register grouping. Check with your NetSuite Admin.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Cashier Workflow</strong></td><td>The base workflow that this one extends.</td><td><a href="/pages/a473DeoiPpQL2j2vS6ZH">/pages/a473DeoiPpQL2j2vS6ZH</a></td></tr><tr><td><strong>PIN Override</strong></td><td>How PIN protection works end-to-end.</td><td><a href="/pages/ZB1p1C3xoZi8Tr9w4b1S">/pages/ZB1p1C3xoZi8Tr9w4b1S</a></td></tr><tr><td><strong>Creating Custom Workflows</strong></td><td>How to clone and modify this workflow.</td><td><a href="/pages/HXAKNURkKoLjhJP3Y3ht">/pages/HXAKNURkKoLjhJP3Y3ht</a></td></tr></tbody></table>


---

# 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.in8sync.com/client-admin-guide/workflow-builder-overview/workflow-examples/store-manager-workflow.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.