Admin → Customer portal edits the customer account presentation. Save draft stores a revision; Publish promotes the saved draft. The on-screen invoice is sample data. Feature-availability cards are read-only and do not activate delivery, accounting, fee posting, payment collection, or a supporting module.
Before you beginUse the intended business and an authorized settings role. Agree on the customer-visible sections, wording and privacy policy before publishing. Keep live customer links and financial data out of screenshots.
Step by step
- Open Admin → Customer portal and wait for settings to load. Confirm the business before changing anything. If loading fails or no draft appears, resolve the error or access issue rather than assuming that default-looking fields are saved settings.
- Read Capability status first. Statements, Subscription requests, Finance charges and QuickBooks lifecycle show availability and operational status separately. Status unavailable, Operational activation off or Worker release pending is not an invitation to enable an integration from this screen; refer the exact state to authorized support when needed.
- Under Portal sections, leave required Account overview and Balances and invoices available. Choose optional Deliveries, Receipt history, Events, Warranties, Payment methods and Loyalty only when appropriate for this business. Disabled optional sections are removed from portal navigation and the public portal response.
- Under Invoice formatting, enter the Heading as plain text, up to 80 characters, and choose an Accent color. Use the available date format deliberately: medium text date, US short date or international short date. Check that the chosen color and wording remain readable.
- Add a plain-text Footer message of up to 500 characters. Review Show item SKUs, customer-facing item notes, customer-facing invoice notes, discount breakdown and tax breakdown individually. Enable only information appropriate for the receiving customer.
- Review Draft preview after editing. The preview uses a sample customer and transaction, so it helps inspect formatting but cannot prove that a real customer has access, a balance is accurate, a feature is entitled, or a payment can settle. Account identity, balances, invoice number/dates, customer/business identity, totals and amount due remain required.
- Choose Save draft and wait for Customer portal draft saved. Reopen or reload and confirm the stored draft and revision. Unsaved browser edits are not the server draft that Publish promotes; save the intended changes before publishing.
- When the reviewed saved draft is approved for customers, choose Publish once. Wait for Customer portal settings published and check Published revision/time. A successful draft save alone does not mean the customer presentation is published.
- Use an authorized controlled customer account to review the published sections and document appearance. Confirm that hidden optional sections are absent and required financial facts remain visible. Check account permissions and feature entitlements separately; presentation changes do not grant another account access.
- If a revision conflict or publish/save error appears, reload the current settings, reconcile other edits and repeat only the intended step. Record the business, approximate time and safe error text for support; never include a private account token or full customer access link.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Save draft | Stores the current normalized presentation as a server draft revision. |
| Publish | Promotes the saved draft using revision checks; it does not first save unsaved browser edits. |
| Capability status | Read-only module and operational status; does not activate providers or workers. |
| Required sections | Account overview and Balances and invoices cannot be disabled here. |
| Draft preview | Sample invoice for formatting review, not live customer or payment evidence. |
| Published revision | Identifies the stored presentation promoted for customers. |
Expected result
The saved draft and published revision are understood separately, approved customer-facing sections/formatting are visible, and capability cards have not been mistaken for activation or payment controls.
Troubleshooting
- Save the intended draft before choosing Publish; a preview change alone does not update the saved revision.
- If a capability reports pending/off/unavailable, retain that boundary and ask authorized support about the underlying module.
- Review the actual authorized customer account after publishing; sample preview data does not establish access or payment readiness.
CentriPOS API explorer · API Center administration
More guides
Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.