Staff, Roles, Sales Channels & Point of Sale

Overview

Running a store is a team sport that often spans more than the web. StretchShop lets you manage staff and roles (with 2FA and an audit log), sell through additional sales channels, run a point of sale for in-person sales, and extend your store with apps and webhooks. This guide covers store operations and access.

Staff and roles

1. Open Settings > Staff to see your team.
2. Click Invite to add a teammate by email, or New staff to create a member directly.
3. Assign a role that determines what they can do. Manage roles under Staff > Roles — create roles, edit permissions, and remove roles you no longer use.
4. For security, toggle 2FA on a staff member, and suspend anyone who should temporarily lose access without being deleted.

Audit log

Open the Audit log to review who did what and when across the store. This is your accountability trail for sensitive changes — pricing, refunds, permissions — and is invaluable during investigations and reviews.

Sales channels

Channels let you sell the same catalog in more than one place.

1. Open Channels and create a channel for an additional surface.
2. Publish products to a channel as listings, and unpublish them when they shouldn't appear there.
3. Use Sync to reconcile a channel's listings with your catalog so availability and details stay consistent.

Point of sale (POS)

Sell in person — at a shop, market, or pop-up — with POS.

1. Open POS > Registers and create a register for a till or device.
2. Open a session at the start of a shift (recording an opening float), take sales as transactions through the day, and close the session at the end.
3. Run the Z-report for a session to reconcile sales and cash at close.

POS sales feed the same catalog, inventory, and reporting as your online store, so stock and numbers stay unified.

Apps and webhooks

Extend StretchShop with apps and event webhooks.

1. Open Apps to install an app; manage its extensions and app-specific webhooks.
2. Configure webhook endpoints so external systems are notified when events happen in your store (for example an order is created), enabling integrations with fulfillment, accounting, or analytics tools.

A realistic example

You hire a fulfillment assistant. You invite them, assign a role limited to orders and fulfillment, and enable 2FA. For a weekend market you create a POS register, open a session with a $100 float, ring up in-person sales as transactions, and close with a Z-report that matches the cash drawer. You also connect an accounting integration by adding a webhook endpoint for new orders, and later review the audit log to confirm who issued a large refund.

Tips

• Give staff the least privilege they need via roles; use suspend for temporary removals instead of deleting accounts.
• Turn on 2FA for anyone who can touch money, pricing, or customer data.
• Close POS sessions and run the Z-report every shift so cash reconciles cleanly.
• Use webhooks to automate hand-offs (fulfillment, accounting) rather than exporting by hand.

Troubleshooting

• A teammate can't do something — check their role's permissions; adjust the role or assign a more capable one.
• Suspended staff still shown — suspension blocks access but keeps the record for history; delete only when truly offboarding.
• Channel listing out of sync — run Sync on the channel to reconcile it with the catalog.
• POS cash doesn't reconcile — compare the Z-report to the drawer; confirm the opening float and every transaction were recorded.
• Webhook not firing — verify the endpoint URL and that it's subscribed to the right event.