Selstack is a platform for creators and businesses to build a public selling page, share individual offers, accept supported payments and bookings, and manage the resulting orders and customer details. A “Stack” is a selling page. This guide explains the relevant workflow and the seller’s responsibilities; payment methods, account requirements and some features depend on the business configuration and plan.
Turn roles, least privilege, payout access, customer data, offboarding and review dates into a repeatable operating process that produces team access that matches responsibility and changes when the team changes.
A repeatable operating routine should connect Selstack orders and customer context to fulfilment, support, finance and team responsibilities.
Define the decision and its owner
Turn the topic into an operating decision rather than a vague aspiration. Document roles, least privilege, payout access, customer data, offboarding and review dates. Name the person responsible, the Selstack record they should check and the status or event that starts the work.
Write the normal path in plain language
Describe the few steps that should happen for a typical order, contact, support request or financial review. Use the authenticated Selstack record as the shared reference. A short process that the team follows is more useful than a large document nobody can apply.
Add controls where errors are expensive
Require a second review for changes involving money, access, customer data or irreversible fulfilment. Separate preparation from approval where possible. Do not share administrator credentials or move sensitive decisions into private messages that leave no reliable history.
Plan the exception path
Write what happens when information conflicts, a payment is pending, stock is unavailable, a deadline moves or a customer disputes the outcome. State who can decide, what evidence is safe to collect and when official support or a specialist must be involved.
Review evidence on a useful rhythm
Use paid orders, fulfilment time, customer questions, refunds, support load and available balances according to the decision. Compare the current period with the same definitions, not a changing collection of vanity metrics. Assign actions and review dates, not only observations.
Keep the process proportional
The target is team access that matches responsibility and changes when the team changes. Simplify steps that add no control and strengthen steps that protect customers or funds. Avoid sharing one administrator login or leaving former collaborators with active access. The process should remain usable when the business is busy or a different team member takes over.
A practical example
Team access is a Pro feature; give each member the narrowest supported role and remove access when responsibilities end.
When the result is unexpected
If Team opens Billing, confirm Pro entitlement instead of sharing the owner login.
Use the workspace as an operating system for the business
A Selstack workspace brings published offers, customer activity and the relevant selling workflows together for one business. That organisation is useful only when the team knows which business it is working in and what each record means. Start an operational task by confirming the active workspace, then choose the appropriate offer, order, contact or report. A creator identity and a business identity are presentation choices; they should not be confused with the permissions or subscription capacity available to a team.
Create a small daily review
Look for customer commitments that need an action: new enquiries, confirmed orders awaiting fulfilment, booking questions and unresolved payment cases. Assign an owner and a next step rather than simply counting the items. Check whether a published offer is still available and whether its public wording matches the current delivery process. A useful daily routine prevents small inconsistencies from becoming repeated customer problems. It should be short enough for the team to follow consistently, not an elaborate checklist that is ignored after the first busy day.
Write instructions around a real task
A working procedure should tell an authorised person how to identify the correct record, what to check, what action they may take and how to confirm the result. Include the relevant exception route. For example, preparing a physical order requires checking payment timing and the selected delivery arrangement; it should not assume that every order was paid online. Keep instructions tied to the current Selstack interface and the business’s actual process. Update them when a repeated question reveals a missing decision.
Give people appropriate access
Review the team members who need access and the responsibilities they will carry out. Use the supported team and permission controls rather than sharing one person’s login. A colleague who needs to answer customer questions may not need authority over every financial or account setting. Plan capacity and available team features depend on the subscription and account state. Review the current plan information before inviting additional people, and remove access when a person no longer has a legitimate role in the business.
Keep account security part of ordinary work
Use strong, unique credentials and the security controls available for the account. Do not put passwords, one-time codes or recovery information into shared notes, forms or customer conversations. If a message requests a sensitive account action, verify it through the established account and support route. A professional-looking request is not proof that the sender is authorised. Keep staff responsibilities clear so an urgent customer issue does not become a reason to bypass the business’s normal access and approval arrangements.
Make hand-offs understandable
When work passes between people, explain the customer’s request, the record checked, the current status and the next promised update. Distinguish a confirmed fact from a possible explanation. Avoid notes that make sense only to the person who wrote them. Keep sensitive information limited to what the task requires and use safe references to locate related records. A clear hand-off lets another authorised team member continue the work without asking the customer to repeat the entire history.
Plan around delivery capacity
Pricing and promotion should reflect the time and resources needed to fulfil the offer. For services, include preparation and follow-up rather than only visible session time. For products, account for packaging, availability and delivery arrangements. For courses and events, consider the support and attendance workflow as well as sales. A successful campaign can create operational pressure if the business has not planned the next stage. Review capacity before promising a deadline that depends on work the team cannot realistically complete.
Review money and activity separately
Sales activity, successful payments, available funds and business profit answer different questions. Use the labelled records and appropriate reporting period when reviewing performance. Keep operating costs in the business’s bookkeeping process rather than assuming a payment report automatically includes every cost of running the business. Preserve references so figures can be reconciled to their source. If a discrepancy appears, investigate the relevant stage before changing a process or making a financial commitment based on an unconfirmed balance.
Close the loop at a regular review
At a weekly or monthly review, examine recurring customer problems, delayed commitments and the effect of recent changes. Choose a manageable improvement and assign responsibility for completing it. Check that published offers, team instructions and customer messages remain consistent. Selstack can connect the records that support daily work, but it cannot replace clear ownership, realistic promises or a team that acts on the information available. A dependable operating routine makes the platform useful to the business and the experience more predictable for customers.
Review Selstack pricing for current plans and online payment fees. For related tasks, visit the Help Centre. If the recorded result remains unclear, contact support with the relevant safe reference.
