Configure the business before users start entering stock or transactions.

Before you begin

• Know the business currency, tax approach, main contact details and first operating location.

Steps

1. Open Settings → Business Settings.
2. Confirm business name and identity details.
3. Set currency plus significant currency and quantity precision.
4. Review tax, invoice and reward defaults.
5. Save the settings, then create or review Business Locations.

What SwiftPOS does

• Currency/precision settings become the formatting and validation basis for later transactions.
• Location records become the ownership boundary for stock, registers and notification delivery.

Prepare users, locations and the cash register before the first POS sale.

Before you begin

• The cashier must be active, have access to the location and have sales/register permissions.

Steps

1. Select the working location.
2. Open Registers.
3. Open the register and enter the actual opening cash.
4. Open POS and confirm the selected customer/location context.
5. Start selling only after the register is open where register control is enabled.

What SwiftPOS does

• Opening cash becomes part of end-of-day counted-cash reconciliation.

Install the web application on a supported phone, tablet or desktop without turning accounting transactions into offline data.

Before you begin

• Use SwiftPOS over HTTPS in a supported browser. Chrome/Edge on Android or desktop can show the install action after sign-in; iPhone/iPad installation uses Safari → Share → Add to Home Screen.

Steps

1. Open SwiftPOS in the browser and sign in.
2. Use the download icon in the authenticated SwiftPOS header when it appears, or use the browser's Install/Add to Home Screen command.
3. Launch SwiftPOS from the new home-screen/desktop icon.
4. Sign in normally; the installed app opens in its own standalone window.
5. If connectivity is lost, reconnect before attempting sales, payments, purchases, stock or other accounting changes.

What SwiftPOS does

• The installed app uses the SwiftPOS icon and green application theme.
• Dashboard, POS, Products and Documentation shortcuts are exposed to supported launchers.
• Only same-origin static assets are cached; authenticated HTML, API responses and accounting transactions are never stored or queued by the service worker.
• When the network is unavailable, navigation falls back to a safe offline notice rather than a stale accounting screen.

Review business performance for the intended period and branch.

Steps

1. Open Dashboard.
2. Select the date range.
3. Select a location or All Locations where permitted.
4. Review sales, receivables, payables, stock alerts and Sales Last 30 Days.
5. Open the underlying report when you need transaction-level evidence.

What SwiftPOS does

• Dashboard cards recalculate for the chosen accessible scope; the Sales Last 30 Days chart remains a rolling recent-day view.

Create an individual or business customer for invoices, statements and payments.

Steps

1. Open Customers and choose Add Customer.
2. Choose Individual or Business.
3. For Business enter the business name; for Individual enter first and last name.
4. Add phone/email/address details as needed.
5. Save the customer.

What SwiftPOS does

• The customer becomes available in POS and conventional sale entry.

Create a supplier before recording supplier purchases or payments.

Steps

1. Open Suppliers.
2. Choose Add Supplier.
3. Enter supplier identity and contact details.
4. Save the supplier.
5. Use the supplier on Purchase Orders or Purchases.

Record money received now against an invoice that may have been issued earlier.

Before you begin

• Open the customer or sale and confirm the invoice balance still due.

Steps

1. Open the customer Sales tab or the Sales list.
2. Choose Pay/Add Payment for the target invoice.
3. Enter the amount actually received.
4. Choose the actual payment method such as Cash, M-Pesa, Paybill, Card or Bank.
5. Apply available customer value only when intentionally using Advance or Return Credit.
6. Save the payment and verify the updated invoice balance.

What SwiftPOS does

• Payment date determines the register collection day; invoice date determines whether it is a current-day sale collection or an older balance collection.

Use stored customer value without confusing it with a new cash receipt.

Steps

1. Record new money in excess of an invoice as an advance when the payment workflow creates/retains customer value.
2. Use Customer Return Credit when value was created by an eligible sale return.
3. When paying an invoice, choose the amount of advance and/or return credit to apply.
4. Do not record a fake Cash payment when only stored customer value is used.

What SwiftPOS does

• Stored value allocations reduce invoice balances but do not represent new cash received into today's register.

Use the contact importer owned by Contacts rather than the retired Data Management screen.

Steps

1. Open Contacts Import.
2. Download/review the expected columns if offered.
3. Upload the source file.
4. Review validation and row-selection results.
5. Import only validated rows and correct rejected records before retrying.

Create a normal sellable stock item with its own price and stock identity.

Steps

1. Open Products → Add Product.
2. Choose Single product.
3. Enter product name, SKU/barcode, category, brand and unit.
4. Enter purchase cost and selling price where permitted.
5. Configure tax, minimum stock and inventory tracking.
6. Save, then add opening stock if this item already exists physically.

What SwiftPOS does

• A simple product owns its selling price and its inventory quantity.

Create a sellable non-stock item without forcing inventory units onto the service.

Steps

1. Open Products → Add Product.
2. Choose Service.
3. Enter the service name, category/brand and selling price.
4. Leave Unit and Selling units blank when the service is simply sold by quantity, or choose a meaningful unit such as Hour, Session, Job or Day when measurement is useful.
5. Configure tax and optional group prices, then save and assign the Service to selling locations.

What SwiftPOS does

• A Service never creates or consumes inventory. Unit and Selling units are optional and affect only how a measured service is presented/sold. Invoices and receipts label a Service with no configured Unit as Service and print its quantity without inventing a unit.

Create a parent catalogue product whose sellable prices and stock belong to exact variations.

Steps

1. Add a product and choose Variable.
2. Save the parent product first.
3. Define/generate the required variations.
4. Give each variation its exact identity/SKU.
5. Set variation price and stock as applicable.
6. Sell the exact variation rather than relying on a vague parent price.

What SwiftPOS does

• The parent organizes the catalogue; each variation is the authoritative sellable entity for price and stock.

Sell one combo at a defined selling price while consuming component inventory.

Steps

1. Add a product and choose Combo.
2. Save/open Combo Setup.
3. Search and select each component product or exact variation.
4. Enter component quantities.
5. Set the combo selling price.
6. Save and sell the combo normally.

What SwiftPOS does

• The combo owns the selling price; cost and stock consumption come from the selected components.

Offer independently priced and stocked add-on products before the selected parent/variation is committed to the POS cart.

Before you begin

• Create every accessory first as a normal active Single or Variable product.

Steps

1. Open the main product and choose Configure Accessories.
2. Create an accessory group and enter its name.
3. Set Minimum, Maximum and Required according to the selection rule.
4. Use the Accessory product search/dropdown as one field to find the eligible product.
5. For a Variable accessory, use Exact variation; SwiftPOS shows only variations that belong to the selected accessory product.
6. Choose Quantity per parent item or Fixed quantity and enter Qty.
7. Set Default/Active where appropriate and save the group.
8. In POS select the parent or any exact variation. SwiftPOS opens the parent accessory groups before adding that sellable line to the cart; choose Skip or Add Selected as allowed.

What SwiftPOS does

• Every sellable variation of a Variable parent inherits the parent product's configured accessory groups.
• Accessory price, tax, selling unit and stock stay on the accessory product/variation.
• Parent-linked quantities scale automatically when Quantity per parent item is used.
• Removing the parent removes its linked accessory lines; receipts and returns preserve the relationship.

Maintain different authorized selling prices for customer/transaction contexts.

Steps

1. Open Selling Price Groups.
2. Create or select the required price group.
3. Set it as default only when it should be the normal business price context.
4. Open product/group prices; clicking a populated price field selects its existing value for immediate replacement.
5. Enter the intended price per sellable entity using the business currency precision.
6. Verify POS uses the expected price group before completing a sale.

Enter starting stock for inventory that existed before SwiftPOS began tracking it.

Steps

1. Open Product Opening Stock.
2. Review each assigned business location and exact variation row.
3. Click an existing quantity/cost field to select its current value, then type the replacement.
4. Enter quantities using the business quantity precision and unit costs using the business currency precision.
5. Enter lot/serial data where the product requires it.
6. Save Opening Stock; after a successful reconciliation SwiftPOS returns to the Products list.

What SwiftPOS does

• Posting creates auditable opening inventory rather than silently changing current stock.
• Quantity and money input/display precision follows Business Settings.

Configure the low-stock threshold used by alerts and replenishment review.

Steps

1. Edit the product or variation.
2. Enter Minimum Stock quantity.
3. Save.
4. Review stock alerts/reorder reports when current quantity reaches or falls below the threshold.

What SwiftPOS does

• Minimum Stock is a threshold only; it does not cap maximum inventory.

Sell stocked products quickly through the POS screen.

Before you begin

• Use the correct location and open register when register control is enabled.

Steps

1. Open POS.
2. Search/scan and select the product or exact variation.
3. If the parent has accessories, choose them before SwiftPOS adds the parent/variation to the cart; every variation of a Variable parent uses the parent's accessory groups.
4. Select/add the customer when required.
5. Review quantities, units, tax, discounts and price context.
6. Choose Pay, enter payment method/amount and complete the sale.
7. Print/view the receipt and remain in POS for the next transaction.

What SwiftPOS does

• Final sale lines reduce stock, payment records feed register reconciliation and the invoice becomes available in customer/sales history.

Create a full customer record without abandoning the current cart.

Steps

1. In the POS customer search choose Add Customer.
2. Complete the customer form in the modal.
3. Scroll inside the modal when the form exceeds the viewport.
4. Correct any required fields highlighted in red.
5. Save Customer; SwiftPOS closes the modal and selects the new customer.

Save a sale without treating every in-progress document as a final stock/payment transaction.

Steps

1. Build the sale lines.
2. Choose Draft when the document is incomplete and intended for later editing.
3. Choose Suspended for a temporarily parked POS transaction.
4. Choose Quotation when presenting an offer before final sale.
5. Resume/convert the saved document and revalidate pricing/stock before final completion.

What SwiftPOS does

• Final status is the point at which normal sale accounting/stock behavior becomes authoritative.

Collect all or part of an invoice after the original sale date.

Steps

1. Open Sales or the customer record.
2. Find the invoice with a due balance.
3. Choose payment.
4. Enter the amount received today and the actual payment method.
5. Apply stored customer value only when intended.
6. Save and verify the remaining balance/status.

What SwiftPOS does

• A cash collection today against an older invoice appears as Balance Paid (Cash) in today's register.

Sell using configured selling units while keeping stock in the authoritative base quantity.

Steps

1. Configure product selling units first.
2. In POS choose the intended selling unit when available.
3. Enter the customer quantity in that unit.
4. Review the converted stock quantity and price before completing.

What SwiftPOS does

• SwiftPOS converts units to the product's stock basis; e.g. 2 dozens consumes 24 pieces when that conversion is configured.

Return selected products from an existing final sale.

Steps

1. Open Sales and choose Return, or open Sale Return and enter the invoice number.
2. Review original customer, date and location.
3. Enter Return Qty only for items being returned.
4. Confirm unit, original tax and proportional discount treatment.
5. Choose the allowed refund/customer-credit outcome.
6. Post the return and verify invoice balance plus stock restoration.

What SwiftPOS does

• Only returned quantities are reversed; shipping remains non-refundable under the current rule.
• Accessory lines remain identifiable with their parent relationship and can reverse their own inventory/value.

Respect the amount actually paid when calculating refund eligibility.

Steps

1. Check the invoice payment status before posting the return.
2. For an unpaid due invoice, do not issue a cash refund for value never received.
3. For a partially paid invoice, keep immediate refund/customer-credit within the legitimately paid refundable value.
4. Post the return and verify the remaining document balance.

Use auditable return and new-sale documents instead of rewriting the original transaction.

Steps

1. Return the original item/quantity using Sale Return.
2. Create a new sale for the replacement item.
3. Apply legitimate customer credit/refund value according to the chosen settlement method.
4. Keep both documents linked through the customer's history/audit trail.

What SwiftPOS does

• Inventory and prices remain historically correct for both the returned and replacement products.

Record a supplier purchase/order with products, costs, tax and expected quantities.

Steps

1. Open Purchases → Add Purchase.
2. Choose supplier, location, date and document reference.
3. Add product/variation lines and quantities.
4. Review unit cost, tax, discounts and totals.
5. Save the purchase.
6. Use Receive Goods when physical stock arrives.

Move purchased quantities into inventory only through Goods Receipt.

Steps

1. From Purchases select Received or choose Receive Goods for the purchase.
2. Review each line's outstanding quantity; Receive Now starts at the outstanding amount.
3. Reduce rows for a partial receipt or set unreceived rows to zero.
4. Enter lot/batch, manufacture/expiry and serial details where required.
5. Post the goods receipt.

What SwiftPOS does

• Partial receipt sets the purchase to Partially received; receiving all outstanding quantity sets it to Received.
• Goods Receipt, not a manually forced status, is the authority that increases stock.

Record money paid to a supplier against purchase liability.

Steps

1. Open the supplier or purchase.
2. Choose Add/Record Payment.
3. Enter amount, payment method and reference/date.
4. Save and verify the purchase/supplier balance.

Return received goods to the supplier and reverse inventory through a controlled document.

Steps

1. Open Purchase Returns or choose Return from the purchase.
2. Select the purchase and eligible lines.
3. Enter return quantities and review values.
4. Post the return when approved.
5. Verify supplier credit/balance and stock reduction.

Know which operational documents increase or decrease inventory.

Steps

1. Use Goods Receipt to increase stock from purchases.
2. Final sales decrease sold stock.
3. Sale returns increase returned stock.
4. Posted purchase returns decrease returned-to-supplier stock.
5. Stock adjustments/count postings create controlled corrections.
6. Completed transfers move quantity from source to destination.

Compare physical quantity with SwiftPOS and post the approved difference.

Steps

1. Open Stock Counts and create a count for the location/scope.
2. Enter physical counted quantities.
3. Review differences before posting.
4. Post only after confirming the physical count and reason.
5. Review resulting stock movements/history.

Record controlled inventory corrections instead of directly editing quantity.

Steps

1. Open Inventory Controls/Stock Adjustment workflow.
2. Select the location and product/variation.
3. Enter quantity and reason.
4. Review value impact where applicable.
5. Post the document and verify stock history.

Maintain traceability for products configured for lot/batch or serial control.

Steps

1. Enable the required tracking on the product before transacting it.
2. Capture lot/batch/expiry or serial identities during receipt/opening stock.
3. Use lot/serial selectors on controlled outbound transactions.
4. Review lot/serial lists when investigating stock.

Investigate quantity/value changes instead of relying only on current stock.

Steps

1. Open the product Stock History or stock-movement report.
2. Select the business location.
3. Search/switch the main product and exact variation where required.
4. Review document source, quantity movement and valuation/cost context.
5. Use integrity/audit tooling for unexplained ledger issues rather than editing history.

Transfer stock between business locations without losing source/destination accountability.

Steps

1. Open Stock Transfers → Add.
2. Select the source location. SwiftPOS disables that same location in Receiving Location so a transfer cannot point back to its source.
3. Select a different receiving location and the required transfer status.
4. Search and add the product/variation to transfer.
5. The existing Available column shows the live source balance as Available: quantity + unit.
6. Click/focus the Quantity field; its current/default value is selected automatically so typing replaces it immediately.
7. Enter the transfer quantity. SwiftPOS validates it immediately against the source balance, gives the quantity field a red border and shows an inline error if the request exceeds availability.
8. Correct any quantity that exceeds source availability; Save remains blocked while a row has a live stock error or its stock check is pending.
9. If Save is attempted with required header fields or transfer lines missing, SwiftPOS marks all invalid fields red and scrolls/focuses the first error.
10. Save as Pending while editable.
11. Move to In Transit when dispatched.
12. Complete/receive the transfer at the destination according to permissions.
13. Review activity history and notes.

What SwiftPOS does

• Live availability is advisory for immediate feedback; SwiftPOS still locks and validates source stock again inside the save transaction so concurrent stock changes cannot bypass inventory protection.
• Status rules protect edits after dispatch and keep source/destination stock movements auditable.

Start a cashier/location register with authoritative opening cash.

Steps

1. Open Registers.
2. Choose Open Register.
3. Confirm the cashier/location context.
4. Enter the actual opening cash placed in the drawer.
5. Open the register.

What SwiftPOS does

• Opening cash is later subtracted from Notes + Coins to calculate net counted cash for the close sheet.

Distinguish current-day cash sales from money collected today for older invoices.

Steps

1. Open Register Detail.
2. Read Total Cash Sales as cash received today against invoices created today.
3. Read Balance Paid in Cash as cash received today against invoices created before today.
4. Review Balance Paid (Other Methods) by its actual payment-method breakdown.
5. Use sale/payment history to investigate differences.

Compare physical cash with the cash SwiftPOS expects from the authoritative register activity.

Steps

1. Open the register and choose Close.
2. Count Coins and Notes physically.
3. Use the info icon beside Register Details to review the counted-cash formula, then compare the calculated left-side total.
4. Review posted cash expenses in the middle column.
5. Use the info icon beside Sales to review the expected-cash formula and non-cash audit treatment.
6. Investigate any variance before completing the close; the info icon beside Variance / overage reason explains the shortage/overage handling.

What SwiftPOS does

• Closed-register reconciliation is frozen as a historical snapshot so later transaction edits do not silently rewrite the close.

Choose the reconciliation scope that matches how physical cash is actually controlled at the location.

Steps

1. Use Own Sales when the cashier/salesperson has an individual cashbox; the close uses that cashier's register-day activity.
2. Use All Location Sales when several salespeople feed one shared physical cashbox; the close uses the location/day sales and payment records for every user.
3. Count the shared cashbox physically, select All Location Sales, review the location total, then close normally.
4. All Location Sales requires the broader sales-view permission in addition to register-close permission.

What SwiftPOS does

• Both scopes can close the register and freeze the selected reconciliation snapshot.
• Under Own Sales, a shortage belongs to the cashier who opened the register. Under All Location Sales, a shortage belongs to the employee who closes the shared cashbox.

Create an auditable expense rather than reducing register cash manually.

Steps

1. Open Expenses → Add.
2. Choose category, Expense For/reporting attribution, payee/payment details and amount/tax.
3. Save/submit according to your approval workflow.
4. Approve when required.
5. Post the expense; use Post & Deduct from Register only for genuine register cash expenses.

What SwiftPOS does

• Posted cash expenses reduce expected register cash when correctly linked to the register.

Create repeatable expense definitions without manually recreating the same setup each period.

Steps

1. Open Recurring Expenses.
2. Create the recurrence with category, amount and schedule.
3. Run due recurring expenses manually or through the configured process.
4. Review generated expense records before/after posting according to permissions.

Review sales, purchases, stock, payments, tax, aging and profitability for the intended scope.

Steps

1. Open Reports.
2. Choose the report type.
3. Set date and location filters.
4. Apply product/customer/supplier/payment filters where offered.
5. Review totals and drill into supporting transactions when needed.
6. Export only after confirming the report scope.

Analyze historical register sessions and payment/cash reconciliation.

Steps

1. Open Reports → Register Report.
2. Select date/user/location scope.
3. Compare register totals with underlying sale/payment/expense history.
4. Use the frozen close snapshot when reviewing a closed session.

Create a staff login with only the business locations and capabilities they need.

Steps

1. Open Users → Add User.
2. Enter identity/login details.
3. Assign the role/permissions.
4. Assign accessible locations.
5. Save and test the user's expected navigation/action access.

Protect business logins with Email/SMS verification and let users recover passwords through their primary work location communication settings.

Before you begin

• Every active user who will use the selected 2FA method needs a Primary Work Location (Default Location), plus an account email for Email or phone number for SMS. Configure that location's SMTP or SMS gateway first.

Steps

1. Open Settings → Business Settings → Security.
2. Choose Email or SMS and enable two-factor authentication.
3. Review the per-user readiness table; SwiftPOS refuses to enable 2FA while an active user is missing the selected channel configuration.
4. After username/password validation, enter the six-digit code sent through the user's primary work location.
5. For a forgotten password, choose Forgot password? on Sign in, select Email or SMS, verify the short-lived code, then set a new password.

What SwiftPOS does

• Verification codes are hashed in the database, single-use, expire after 10 minutes and are rate-limited.
• Email transport uses the user's primary location SMTP settings; SMS transport uses that location's configured SMS provider/gateway. Security SMS numbers are normalized to Kenyan international MSISDN format beginning with 254 before transmission. The destination is the user's own email or phone number.

Bundle business permissions into a reusable staff role.

Steps

1. Open Roles.
2. Add or edit a role.
3. Select only the required permissions.
4. Pay special attention to Own vs All sales/purchases/expenses permissions.
5. Save and assign the role to users.

Prevent a user's list/report scope from exceeding their responsibility.

Steps

1. Use View Own Sales/Purchases/Expenses for users who should see only their own activity.
2. Grant View All only to users who need broader authorized business/location visibility.
3. Remember that location assignment still constrains access.
4. Test sensitive lists/reports after changing a role.

Read and manage the application's operational alerts.

Steps

1. Open Notification Centre.
2. Review unread notifications.
3. Open a notification to its related context.
4. Mark items read/archive as appropriate.
5. Use Preferences/Alert Settings to control supported notification behavior.

Give each branch its own outbound SMS gateway and SMTP identity.

Steps

1. Open Settings → Locations → Edit the location.
2. On SMS configure gateway URL, request method/payload, recipient/message parameter names, headers and extra parameters.
3. Use Test SMS after saving.
4. On Email configure SMTP server, credentials/security and sender.
5. Use Test Email after saving.

What SwiftPOS does

• Customer Order received, Payment received and Payment reminder messages use the location attached to the sale/payment, so branches can send through different transports.

Control supported customer/supplier notification wording and tags.

Steps

1. Open Message Templates.
2. Choose the notification/template type.
3. Edit subject/body and supported template tags.
4. Save and test through the relevant business workflow.

Control display and validation precision without rewriting historical transaction facts.

Steps

1. Open Business Settings.
2. Review currency and significant currency precision.
3. Review quantity precision separately.
4. Save.
5. Test a representative product/purchase/sale entry before broad operational use.

Set invoice schemes and defaults before issuing customer documents.

Steps

1. Open Invoice Settings.
2. Create/edit the required invoice scheme.
3. Set prefixes/sequences/layout options as supported.
4. Choose the default scheme where appropriate.
5. Preview/test before issuing live documents.

Maintain tax rates centrally and apply them to products/transactions according to permissions.

Steps

1. Open Tax Profiles.
2. Add/edit the required tax rate/profile.
3. Set the product tax configuration.
4. Review tax on sales/purchases before posting.

Keep public marketing/help content discoverable while operational accounting screens stay out of search results.

Steps

1. Public search indexing is opt-in, not automatic.
2. The anonymous home page, Packages catalogue and Documentation centre are the approved indexable routes.
3. SwiftPOS generates /sitemap.xml only from that public registry.
4. Operational pages such as Products, Sales, Purchases, Reports and Settings return noindex/noarchive directives and are excluded from the sitemap.
5. When adding a genuine public landing page, add it to the central SEO registry deliberately rather than exposing an application namespace.

What SwiftPOS does

• Canonical URLs strip tracking query strings.
• Public pages publish Open Graph/Twitter metadata and JSON-LD schema.
• robots.txt advertises the sitemap while disallowing operational namespaces.

Prepare business/environment credentials and entity mappings before submitting tax documents.

Steps

1. Open KRA eTIMS settings.
2. Save environment credentials and test the connection.
3. Configure location mapping.
4. Configure tax mappings.
5. Map products and customers where required.
6. Synchronize reference codes and validate products/preflight.
7. Review eTIMS logs after submissions.

Create a managed application backup before high-risk administrative changes when policy permits.

Steps

1. Open Backups.
2. Choose Create Backup.
3. Wait for completion and verify the backup appears in the list.
4. Download/store according to your organization's retention policy.
5. Do not treat application source ZIPs as database backups.

Import data from the screen that owns that business object.

Steps

1. Customers/Suppliers → Contacts Import.
2. Products → Product/Variation/Price import tools.
3. Purchases → Purchase Import.
4. Sales → Sales Import when applicable.
5. Review validation and select only accepted rows before committing.

Know which sellable entity owns the selling price.

Steps

1. Simple product → use the product price.
2. Variable product → use the exact variation price.
3. Combo product → use the combo selling price; components determine cost/stock consumption.
4. Accessory → use the accessory product/variation's own price.

Understand how invoice and payment dates affect register totals.

Steps

1. Classify a payment into today's activity by the local business/payment datetime.
2. If the invoice was created today, cash received today contributes to current-day cash sale collection.
3. If the invoice predates today, cash received today contributes to Balance Paid (Cash).
4. Non-cash methods remain itemized by their actual payment method.

Keep inventory reversal separate from the maximum money that can legitimately be refunded.

Steps

1. Return only quantities actually sold and not already fully returned.
2. Recalculate tax/discount from the original sale rules.
3. Do not refund non-refundable shipping under the current rule.
4. Cap immediate refund/customer value by legitimately refundable paid value.

Use posted inventory documents rather than direct quantity manipulation.

Steps

1. Receive purchases through Goods Receipt.
2. Correct physical differences through stock counts/adjustments.
3. Move locations through Stock Transfer.
4. Investigate quantity/value drift through stock history and integrity audits.

Maintain employee records and generate auditable payroll periods.

Steps

1. Create/maintain Employee profiles.
2. Record attendance/shifts/leave as used by your business.
3. Review allowances, deductions, salary advances and approved adjustments.
4. Generate payroll for the intended period/group.
5. Review payroll detail before recording payment.
6. Reverse/correct through supported payroll actions rather than editing paid history.

Keep requested/approved employee adjustments separate from ordinary register/payment data.

Steps

1. Open Salary Advances or Adjustments.
2. Review request, employee, amount and reason.
3. Approve/reject according to permissions.
4. Confirm the approved item is consumed by the intended payroll period.

Capture a lead, schedule activities and convert qualified business into a customer/workflow record.

Steps

1. Open CRM Leads and add the lead.
2. Assign source/pipeline/stage.
3. Add follow-up activities.
4. Move stages as work progresses.
5. Convert the lead when qualified and verify the resulting customer/business linkage.

Consume recipe inputs and create production outputs through an auditable manufacturing document.

Steps

1. Configure Manufacturing Settings.
2. Create/maintain the Recipe/BOM with inputs, outputs and operations.
3. Create a Work Order from the recipe.
4. Review planned quantities and available input stock.
5. Update actual lines as permitted.
6. Post the Work Order when production is complete.
7. Review production report and inventory movements.

What SwiftPOS does

• Posted production consumes configured inputs and creates configured output stock according to manufacturing rules.

Configure one store connection and validate product/order synchronization rules.

Steps

1. Open WooCommerce Stores and add/edit the store.
2. Enter API credentials and test the connection.
3. Configure Product Sync settings including price group/tax/description targets.
4. Provision/review order webhooks.
5. Run product sync and review sync logs.
6. Review imported orders and retry failed items only after correcting the cause.

Mirror SwiftPOS accessory groups on the WooCommerce product page while keeping every accessory as an independently priced and stocked product or variation.

Before you begin

• Configure and save the parent product's accessory groups in SwiftPOS.
• Assign the parent and every accessory product to the WooCommerce store location.
• The accessory product/variation must be eligible for normal WooCommerce Product Sync.

Steps

1. Open WooCommerce → Product Sync and download the SwiftPOS WooCommerce Accessories companion plugin.
2. In WordPress install and activate the companion plugin.
3. Run Product Sync. SwiftPOS first creates/updates normal product and variation mappings, then publishes parent/accessory relationships in a second pass.
4. Open the parent product in WooCommerce and confirm required/optional accessory groups are shown.
5. Place a test order. Per-parent accessory quantities should follow the parent quantity; fixed accessory quantities should remain fixed.
6. Confirm the imported SwiftPOS sale shows the accessory linked beneath its parent on receipts and returns.

What SwiftPOS does

• The relationship metadata carries SwiftPOS option/group IDs and WooCommerce product/variation IDs only; WooCommerce reads the accessory's actual price and stock from the independently synchronized accessory item.
• Incoming WooCommerce orders are validated against the current SwiftPOS accessory configuration before stock is posted.