Standard Operating Procedures
This page is the running explanation for why each function exists in Beach Blend Inventory, who it supports, and how the team should use it. As we add features, this page should be updated alongside the code.
Create named API keys
We are doing this so we can provide functionality to different parts of the organization while still controlling who has access to what. Instead of one shared secret for every internal tool, each workflow can have its own named key.
Why this matters
- The warehouse can have its own key for receiving and stock movement tools.
- Store-side reporting or operations tools can use separate keys.
- If one workflow changes or loses access, we can rotate only that key instead of disrupting every system.
- Named keys make it easier to understand what each integration is for when we review access later.
How to use it
- Open the API Keys page from the embedded Shopify app.
- Enter a clear name that matches the function, such as Warehouse Scanner or Store Reporting.
- Add a short description that explains who or what system will use the key.
- Create the key and copy it immediately. After the first view, only the prefix and last four characters remain visible.
- Store the key in the correct internal system and do not reuse one key across unrelated workflows.
- Delete a key when a workflow is retired or access should be removed.
Detailed SOP pages
Open the dedicated SOP page below for the new vendor inventory API.
SOP maintenance rule
Every time we add a new function to this app, this SOPs page should be updated with:
- Why the function exists
- Who it supports
- How to use it correctly
- Any access or operational cautions that matter for the team