Questions about setting up and running Pryseflow

Pryseflow is a company-scoped business operations and commerce application for products, inventory, warehouses, customers, vendors, estimates, invoices, payments, expenses, bills, contracts, POS, Marketplace, Online Store, staff access, and reports.

The dashboard provides navigation and supported summaries for products, stock, sales, finance, contracts, staff, notifications, settings, reports, and the active company. Available modules depend on plan and configuration.

Pryseflow Marketplace helps customers discover products across multiple sellers. A Pryseflow Online Store is the dedicated ecommerce destination for one business. Both use supported Pryseflow catalogue and order records.

Yes. Onboarding can cover company setup, catalogue import, warehouses, customers, vendors, finance settings, contracts, POS, Marketplace, Online Store, staff, and reporting. Scope and availability are confirmed before work begins.

Current AI Insights is an owner-only, read-only deterministic experience for supported revenue, invoicing, cash-collection, stock, and product-data questions. It returns evidence and authorised report links and does not change records.

Create or import products with categories, attributes, options, images, SKUs, barcodes, units, and prices. Inventory then tracks supported quantities and movement by warehouse for the workflows using those products.

Yes. Pryseflow supports estimates with public approval or decline and invoices with items, tax, discounts, due dates, public links, recorded payments, refunds, status, and invoicing reports.

Invoice and checkout payments depend on the configured provider, country, currency, company, plan, and approval status. Repository evidence includes Paystack, PayPal, and PayFast flows, but availability must be confirmed.

Yes. Expenses and bills can retain vendors, categories, line items, quantities, tax, totals, due dates, status, payment context, and expenditure reporting.

No. Contracts can capture value and recurring-value information, but current product documentation says contracts do not automatically generate invoices.

Pryseflow POS uses company products and supported stock records while retaining shifts, receipts, refunds, register activity, and reporting. Native client, hardware, operating-system, and offline behavior must be verified per deployment.

Customers connect to estimates, invoices, payments, refunds, and contracts. Vendors connect to purchase orders, receiving, expenses, bills, and related reports.

Pryseflow has a verified baseline for staff, POS, register, product, report, staff-management, and sale-void permissions. Permission coverage varies by domain and should not be treated as record-level control everywhere.

The Reports Centre covers revenue, products, invoicing, expenditure, contracts, customers, vendors, warehouses, POS, Marketplace, and staff using authorised company records.

Use the support contact page for an existing account or sign in for account-specific help. Use sales, onboarding, or workflow review when you are evaluating or configuring Pryseflow.

Compare the current plan catalogue for company and user limits, included modules, commerce channels, support, billing frequency, tax, and upgrade rules. Confirm any configuration-dependent feature before purchase.

The configured billing provider and Pryseflow subscription rules determine retries, notifications, grace periods, and access changes. Review the current billing terms or contact support for an account-specific answer.

Annual billing and any discount depend on the current published plan catalogue. Compare the total annual charge and included features rather than relying on an older monthly equivalent.

Pryseflow authenticates users, resolves an active company on the server, applies ownership, role, permission, policy, verification, and account-state checks, and scopes supported records to the authorised company.