FAQ

How is Nexpura priced?

See the public pricing page for current plans and what each plan includes. The billing surface itself — how a tenant subscribes, how to change plan, what happens on a card decline — is documented under Billing and subscription.

Is there a free trial?

Yes — new tenants can try Nexpura before adding a payment method. See the pricing page for the current trial length and conditions, and Account setup for the sign-up flow.

Can I change plan mid-month?

Yes. Upgrades take effect immediately and the difference is prorated on the next invoice; downgrades take effect at the next billing cycle so you keep the higher-tier features for the period you've already paid for. See Billing and subscription for the change-plan flow and what each plan includes today.

Do you offer multi-location or per-staff pricing?

The plan structure on the pricing page is the current shape. For multi-store retailers with operations across several locations, the right next step is a conversation — see Contact us to set up a call and we'll talk through the right shape for your business.

What payment methods do you accept for the subscription itself?

Credit and debit cards processed through Stripe. We don't take bank transfers for the subscription itself today. Card details are stored on Stripe's side, not in Nexpura — see Security for the broader security shape.

Can I cancel any time?

Yes. Cancellation stops the next renewal; the tenant stays usable through the end of the period you've already paid for. After that the account moves to a suspended state — the data is retained per the privacy policy retention window, so you can re-subscribe and pick up where you left off, or export your data first (see the data-ownership question below).

I'm switching from a legacy jewellery system — what does the move look like?

The shape depends on which system you're moving from. The switching page lists the systems we've built importers for and the migration status for each. For the data side specifically — what file shape, what gets imported, what doesn't — see Data import.

For systems we don't have a built importer for, we run an assessment first — share the export shape (a sample CSV, a database dump, or a screen walkthrough of the source system) and we'll tell you what's practical to bring across and what won't fit cleanly. See Contact us to start that conversation.

What data is typically migrated and what isn't?

The everyday core moves across cleanly: inventory items with stock counts, customers with contact and history fields, suppliers, open repairs and bespoke jobs, historical invoices and quotes. The shape that's lossier is the long-tail workflow data — custom fields that don't map to a Nexpura concept, deeply nested category trees, free-form notes attached to records. That's not a Nexpura limitation specifically; it's the cost of any system migration. See Data import for the importable-shape detail.

How long does a migration take?

The data import itself runs in minutes for most tenants — the file goes through validation and loads in batches. The longer part is on the pre-import side: getting the export from your current system into a shape Nexpura can read, spot-checking the imported records, and walking your team through the new product. A typical switch from a small-business system runs over one or two weeks of part-time effort.

Larger or higher-volume migrations get a guided call — see Contact us and we'll work through the timeline together.

Can I run Nexpura alongside my current system for a while?

Yes, and it's the recommended shape for any business that runs more than a few sales a day. The pattern: import your current data into a Nexpura tenant, run both systems in parallel for a week or two while staff learn the new workflow, then cut over the POS register on a specific date. During the parallel period, new sales go through the live system (whichever you're cutting from); Nexpura serves as the read-only reference for everyone training on the new product.

Who owns the data I put into Nexpura?

You do. Your tenant's data is your business data; Nexpura is the steward, not the owner. The privacy policy and the terms of service cover the legal shape. The product-side guarantee is that you can export your data in a usable format at any time — see the next question.

How do I export my data?

See Data import and export for the per-tenant export shape — which tables are included, the file format, and how to trigger the export. The shape is designed to be portable: CSV for the everyday tables, with one CSV per table type so you can open them in Excel or load them into another system.

The same page documents what isn't yet automated. If your needs go beyond the current export surface, get in touch.

What happens to my data if I cancel?

The data is retained per the privacy policy retention window after cancellation — long enough for you to re-subscribe or change your mind, and long enough to fulfil any obligation that requires the records to still exist. After the retention window, the tenant's data is deleted from the production database and from any backups within the standard backup-retention cycle.

The right move before cancelling is to export what you want to keep — bookkeeping records, customer lists, inventory ledger. The export is available at any time the tenant is active.

Where is my data stored geographically?

Nexpura's production database and file storage are hosted in a specific region; the detail (which region, which provider) lives on the security page so it stays as the canonical source. If you have data-residency requirements that the current region doesn't satisfy — common for EU customers with strict GDPR posture, or for jurisdictions that require local storage — see Contact us.

Can I get an API or programmatic access?

Today the supported programmatic-access surface is the per-tenant CSV / data export, plus the specific integrations we've built directly (Shopify, WooCommerce, Mailchimp, Xero, Google Calendar, WhatsApp via Twilio). A public REST or GraphQL API is on the build list — see Data import and export for the current state of what's available.

How does Nexpura handle security in general?

See the security page for the broader posture — how data is encrypted in transit and at rest, how authentication works, what auditing and logging happens, what certifications and compliance shapes apply. The feature-level security pieces (2FA enrolment, the manager PIN, role-based permissions, tenant isolation) live under Security and 2FA and Team and roles.

Can different team members see different things?

Yes — roles and permissions drive what each staff member can see and do. The shape is owner / manager / salesperson / workshop, with role- specific access to financial reports, customer data, settings, and destructive actions. See Team and roles for the per-role matrix and how to invite or change roles.

Is 2FA required for everyone?

2FA is optional per-staff member today; some actions (e.g. owner-level destructive operations) prompt for a manager PIN even without 2FA. The shape is configurable per tenant. See Security and 2FA for enrolment, recovery codes, and the PIN-gated action list.

What if a staff member leaves the business?

Remove their access from /settings/team — the team-member record stays for the audit trail (so prior actions still resolve to a name on the activity timeline) but they can no longer sign in. If they were the owner, see Team and roles for the ownership-transfer flow.

Can I see who did what?

Every long-lived record (repair, bespoke, task, customer, inventory item) has an activity timeline that records state changes with actor and timestamp. See the cross-section pattern on Common issues for how to read it on any surface. Tenant-wide audit reports (cross-record, time-bounded) live on the financials hub for financial-shaped audits — see Financials hub and reports.

How is Nexpura different from the legacy jewellery systems I've looked at?

The honest answer: Nexpura is built for the modern shape of how jewellery businesses run today. The legacy systems have decades of feature accumulation and are extremely deep on niches Nexpura isn't yet — every accountant-side configuration, every tax-code variation, every regional regulatory integration. If your business depends on the deepest version of those niches, the legacy system has more surface to lean on.

What Nexpura is shaped for, and what comes through clearly, is the everyday workflow of a modern jewellery business: a fast POS register on a tablet, a workshop that handles repairs and bespoke and appraisals in one inbox, a clienteling layer that remembers anniversaries and high-value customer histories, a verify-passport surface for piece provenance, and customer-facing pages that don't embarrass the brand. The trade-off is feature breadth for shape and pace.

If you're evaluating, the right next step is a walk-through of your specific workflow with us — see Contact us to set one up. The features pages at /features cover the breadth at a glance, and these docs cover the depth one feature at a time.

Why are some workflows one big page (inventory overview) while others split into many small pages (workshop, integrations)?

The split tracks the underlying complexity. Inventory has one main mental model (items, stock, locations) and several specific surfaces that share it; one overview plus per-surface depth reads well. Workshop has three distinct pipelines (repair, bespoke, appraisal) plus the unified intake — each has its own pre-shipped shape, and the docs follow. Integrations split per-platform because the questions are platform-specific: Shopify-side setup has nothing in common with Xero-side setup beyond both being integrations.

The shape is reader-first: each page is at the right grain for the question the reader actually asks. The cost is the docs feel uneven in length — that's deliberate.

Why does the product talk about “tenants”? Isn't a tenant just my business?

Yes. “Tenant” is the engineering word for “the data and configuration that belongs to one business on the platform.” You see the word in a few places in the docs because it's the precise term for the boundary — your data never crosses into another tenant's, settings are tenant-scoped, billing is per tenant. In everyday speech in the app you'll see “your business” or “your store” instead.

Why does the docs site disclose things that don't quite work yet?

Because hiding them is worse. A docs site that describes a feature as working perfectly when in practice it has a known limitation puts the reader on the wrong foot — they hit the limitation in real use, and now the docs are the first thing they don't trust. The honest in-context disclosure model is more useful: each page describes what's shipped, and where there's a known partial shape or current limitation, the page surfaces it inline alongside the workflow it affects. The reader knows what to expect; the docs stay honest.

The pattern means a few pages carry a small “Honest disclosure” section near the top — those are the surfaces where the in-context note matters most. The aggregation lives in cross-links, not in a stand-alone “known limitations” page; the canonical-page disclosure is the source of truth.

What's currently in active development?

The honest answer: the surfaces marked as partial in the docs are the surfaces with active work in flight. Each canonical page documents what works today and what's being shipped next, in context. The list below links to those pages — for the current state of each, follow the link and read the in-context disclosure on the canonical page. We don't aggregate the disclosure prose here because the canonical page is the source of truth and the only place we promise to keep up to date.

• Anniversary and reminders — anniversary reminder cron evaluation
• Clienteling workflow — clienteling-nudge cron wiring
• Marketing automations — per-automation cron-wiring state
• Campaigns (bulk send) — campaign scheduling shape
• Intake workspace — structured gem fields, identity capture, pickup-counter and photo-at-intake polish
• Memo return or buy — the Convert-to-Owned-Stock button state
• Data import and export — public REST / GraphQL API
• WhatsApp via Twilio — customer-channel routing shape
• Task templates — one-click apply from the new-task form
• Storefront subdomain — checkout layer

Can I request a feature?

Yes, and the feedback shapes the roadmap. The fastest channel is the support email — see Getting help. Describe the workflow you're trying to support, not just the feature name; the underlying need usually points at a clean shape that fits the product. Requests with a real shop workflow behind them get prioritised over abstract asks.

Is there a public roadmap?

There's no public roadmap document today — the docs site is the practical replacement. The partial-status pages above are the things being worked on now. Once they ship, the page status flips to shipped and the disclosure section goes away. New features that aren't yet in the docs are ones that haven't started yet.

Where do I find what changed recently?

The docs site is re-audited on a fixed cadence and each page carries a “last verified” date. A change-log surface is on the build list; today the practical signal is to check the docs page for the feature you care about — if its status or its in-context disclosure changed, the feature changed.