Working in Sales

Daily Operating Model

Sales works best when teams treat the module record as the source of truth and use tasks, tickets, workflows, and reports as supporting surfaces. The flows below are the common day-to-day paths to validate during setup and train users on after go-live.

Flow 1: Create a sales order

1. Open Orders or POS from the Sales launchpad.
2. Select customer, store, and sales channel context.
3. Add products or variants with quantity and price.
4. Review tax, discounts, and total amount.
5. Save the order as draft or confirm according to policy.
6. Trigger stock reservation, payment, or approval workflow if configured.
7. Share confirmation with the customer.
8. Track the order from processing through delivery.

Flow 2: Operate POS selling

1. Open POS and select the store or register context.
2. Scan or search for products and variants.
3. Confirm available stock and price.
4. Add customer details when required for receipts, loyalty, or billing.
5. Collect payment through the configured payment method.
6. Complete the order and print or send receipt.
7. Handle cancellations or refunds through controlled actions.
8. Close the shift with totals and exception notes.

Flow 3: Fulfill an order

1. Open the confirmed sales order.
2. Check order items, stock location, and fulfillment status.
3. Move order to processing when picking starts.
4. Ship or deliver items and capture tracking or delivery notes.
5. Update fulfilled quantities when partial fulfillment is allowed.
6. Notify customer or sales owner on shipment or delivery.
7. Trigger billing, finance, or inventory updates after fulfillment.
8. Review stuck orders from reports or workflow tasks.

Flow 4: Manage exceptions

1. Filter orders by pending approval, payment failed, stock issue, or refund requested.
2. Review the order timeline and status-change events.
3. Create tasks for inventory, finance, or customer support.
4. Approve, cancel, refund, or reschedule only through permitted actions.
5. Document the reason for every exception action.
6. Use reports to identify stores or products causing repeat issues.
7. Update store settings or inventory thresholds when patterns emerge.
8. Close the exception after customer and finance records agree.

Day-To-Day Controls

• Start from the launchpad route, then use filters and saved views to focus on records needing action.
• Use status fields and lifecycle actions instead of free-text notes for important state changes.
• Attach documents, comments, or related records when a decision needs evidence.
• Create tasks when work leaves the current owner or needs a due date.
• Create tickets when the work is customer-facing or belongs in a support/service queue.
• Use workflows for predictable notifications, approvals, escalations, and cross-module updates.
• Use reports for recurring team reviews rather than exporting ad hoc lists every time.
• Keep permissions tight enough that users see the records they need but not sensitive configuration.
• Review rejected, cancelled, failed, or overdue records every week.
• Keep integrations aligned with the same lifecycle users follow in the UI.

Exception Handling

• If a record is stuck, check owner, status, required fields, approvals, and linked records before editing downstream data.
• If a workflow did not run, confirm the event name, trigger filter, record permissions, and service-user access.
• If reports look wrong, inspect whether the source record is draft, cancelled, archived, or missing a required dimension.
• If an integration created bad data, fix the source mapping and then repair the affected records through supported actions.
• If users cannot see a route, review launchpad access, module roles, page permissions, and tenant feature flags.
• If a public or embedded route exposes too much, disable exposure first and then correct permissions or filters.
• If two modules disagree, choose the module that owns the lifecycle as the source of truth and update the other from it.
• If a record supports audit, void, archive, or cancel it instead of deleting it whenever possible.

Reporting Rhythm

• Daily: review new, overdue, failed, rejected, and pending-approval records.
• Weekly: review owner workload, aging, status changes, and recurring exceptions.
• Monthly: review configuration, permissions, integration failures, and report definitions.
• Quarterly: review whether custom pages, workflows, and API access still match real operating practice.
• After major process changes: rerun one end-to-end flow with a pilot record before enabling it broadly.

Cross-Module Handoffs

• To Base objects: pass stable identifiers, owner, status, dates, and any dimensions required for reports.
• To tasks: include a precise action, due date, source record link, and escalation owner.
• To tickets: include requester, priority, support context, and the module record link.
• To workflows: prefer explicit create, update, approval, and status-change triggers.
• To reports: keep dimensions consistent across records so dashboards can group accurately.
• To integrations: use /reference/sales for namespace and intent details.