Using WooCommerce Products in POS and Invoices

Overview

Products and services are central to both invoicing and point-of-sale workflows. When OneSuite is used with WooCommerce, WooCommerce may provide the product catalog that supports item names, prices, categories, tax behavior, and ecommerce order context. OneSuite then allows staff to use those approved products in practical business workflows such as creating invoices, processing POS sales, reviewing receipts, and serving customers.

Business Value and Typical Use Cases

Add a standard product or service to an invoice without retyping the description each time.
Sell approved products through the POS register.
Use consistent pricing between online store, counter sale, and invoice workflows.
Help cashiers and billing staff work from the same product catalog.
Improve customer service by connecting products sold, invoices issued, and payment history.

Before You Begin

Confirm the product catalog has been reviewed by an administrator.
Confirm the user has access to Payments or POS.
Confirm whether the business uses WooCommerce as the product source.

Prerequisites and Permissions

Active OneSuite installation or trial.
User role with access to invoices or POS.
WooCommerce product catalog where WooCommerce is part of the commerce workflow.
Current production release interface.

Concepts

A product catalog is more than a list of things for sale. It controls how staff describe what is being sold, what price appears to the customer, which category the item belongs to, and how taxes or discounts may apply. When a business sells both online and in person, using a shared catalog helps reduce confusion.

In invoicing, products and services become line items. In POS, products become register items. In customer history, those products help explain what the customer purchased, what they were billed for, and what receipts or payments belong to the transaction.

WooCommerce should be mentioned in this documentation because many WordPress-based businesses already use WooCommerce as their product and ecommerce foundation. OneSuite should document how that foundation relates to staff-facing workflows without exposing hidden technical details or unreleased behavior.

How This Feature Fits Into OneSuite

Payments connect directly to invoices, customers, receipts, payment history, and reporting. A payment should always be reviewed in the context of the customer and the invoice or transaction it belongs to.

Products and services may originate from the OneSuite/WooCommerce commerce foundation where configured. This allows catalog information to support POS and invoice line-item workflows without forcing staff to recreate the same sellable item repeatedly.

Screen Orientation

Payments documentation should be read as part of the complete billing lifecycle: identify the customer, create or locate the invoice, present the amount due, receive or record payment, issue the appropriate receipt, and confirm the customer history reflects the outcome.

Do not treat payment status and invoice status as interchangeable. One describes the state of the billing document and the other describes money received or still due. Review both when reconciling customer balances.

Before using online payment functions, confirm the required payment provider connection and organization settings are complete. Staff should never improvise payment configuration during a live customer transaction.

Open the area described in this guide and pause before editing. Identify the page heading, primary action button, search/filter controls, record list or detail panel, status indicators, and any related-record or history areas. This quick orientation prevents users from applying instructions to the wrong record or module.
When the page contains both a list and a record/detail view, use the list for discovery and the detail view for action. Search or filter first, then open the exact record and verify identifying information before making changes.

Role-Specific Guidance

Billing staff create and review invoices, collect or record payments, and confirm receipts and payment history.
Managers review exceptions, aging, failed or incomplete workflows, and daily billing activity rather than editing every transaction themselves.
Administrators maintain payment-provider configuration, user permissions, and company-level settings that billing workflows depend on.

Step-by-Step Instructions

Before creating invoices or POS sales, review the product catalog used by the business. Confirm the item name, price, category, and tax treatment are correct.
For invoices, open Payments and start or edit an invoice. In the line item area, select the approved product or service where the interface provides a product selector. If a manual description is used, make sure it matches the approved catalog language.
For POS, open the register screen and review available products or categories. Select the correct item and confirm quantity, price, discounts, tax, and total before completing the sale.
For ecommerce orders, review WooCommerce order information where applicable, then continue follow-up, billing, communication, or customer service from the OneSuite customer record when available.
After completing the transaction, confirm that the invoice, POS receipt, payment record, or customer history reflects the correct item and total.

Expected Results

After completing these steps, products and services used in invoices or POS should be clear, consistent, correctly priced, and connected to the appropriate customer-facing transaction record.

Verification Checklist

Confirm the correct OneSuite user is signed in and the expected role/permissions are active.
Confirm the customer, company, invoice, product, message, appointment, employee, or other record shown on screen is the one intended for the task.
After saving or completing the action, refresh or return to the relevant list and verify the new status, history entry, balance, message, appointment, or record appears where expected.
Verify invoice customer, line items, quantities, price, tax/discount treatment, total, status, and payment history before communicating a balance to the customer.
Verify product name, price, availability/status, category, and any workflow-specific visibility before beginning a live transaction.

Business Workflow

Administrator approves product in catalog → Billing user adds product to invoice → Customer receives invoice → Customer pays online or by recorded payment → Receipt and payment history are available.
Administrator approves product in catalog → Cashier sells item through POS → Payment is collected → Receipt is issued → Customer history can be reviewed where customer details are attached.

Real-World Business Scenarios

Shared catalog workflow: maintain the approved sellable item in the supported commerce/catalog foundation, then use that item consistently in the OneSuite POS or invoice experience where configured.
Customer service workflow: use customer/order context to understand what was purchased online or in person before creating a new sale, invoice, refund/escalation record, or follow-up.
Catalog troubleshooting: verify the underlying product exists and is correctly configured before treating a missing POS or invoice item as a transaction-screen problem.

Advanced Operational Guidance

For repeatable business work, standardize naming, ownership, tags/statuses, and staff responsibilities before increasing volume. Consistency makes OneSuite search, reporting, history, and handoffs substantially more useful.
When multiple modules participate in the workflow, verify each handoff. Do not assume that completing one screen automatically proves the customer, payment, communication, or reporting outcome is correct elsewhere.
Use the Invoices registry as the source for operational review. Search and status filters should be part of the daily billing routine so duplicate invoices and missed follow-up are less likely.
Avoid maintaining separate unofficial product lists for POS and billing when the supported WooCommerce/OneSuite catalog relationship is intended to provide a shared product foundation.

Screenshots

Production screenshots appear here only after approved OneSuite captures are attached. Written instructions are complete without screenshots.

Best Practices

Use catalog products for repeatable charges and manual line items only when the charge is unusual or custom.
Keep service names customer-friendly, especially when invoices are emailed or printed.
Train cashiers and billing users on the same product naming standards.
Review product categories so POS navigation remains fast and clear.
Use test transactions when confirming a catalog change before relying on it during live sales.

Common Mistakes

Using one vague item called miscellaneous for many different charges.
Changing a product price in one sales channel but not reviewing how it appears in invoices or POS.
Forgetting that taxes, discounts, and quantities can change the final total even when the product price is correct.
Creating separate products for the same item with slightly different names.

Troubleshooting

Symptom: the wrong product appears on an invoice or receipt. Cause: a user may have selected the wrong catalog item or manually typed an unclear line item. Solution: edit the invoice if allowed, void or correct the sale according to business policy, and review the product catalog. Verification: the corrected invoice or receipt shows the right product name and total.
Symptom: POS categories feel crowded or confusing. Cause: product categories may not be organized for cashier use. Solution: review WooCommerce or catalog categories with the business owner or administrator. Verification: cashiers can find common items quickly.
Symptom: online store price differs from invoice or POS price. Cause: catalog settings, sale pricing, manual discounts, or channel-specific pricing may be in use. Solution: review the product record and transaction details. Verification: the customer-facing total matches the intended price and policy.

Frequently Asked Questions

Should every invoice line item come from WooCommerce?: Not necessarily. Standard products and services should use the approved catalog when available, but custom billing may require manual line items.
Why mention WooCommerce in POS documentation?: Because WooCommerce can be the product source for businesses that sell online and through OneSuite POS.
Can a service be a WooCommerce product?: Many businesses represent services as catalog items so they can be invoiced or sold consistently.

Next Steps

Continue with the Related Articles section to follow the workflow into the next OneSuite function instead of returning to the homepage after every task.

Last Updated: August 21, 2026
Version: 0.3.2-Phase2B-SHORTCODE-RENDER-RECOVERY
Verified Public Source Baseline: PASS35H66DN RC1 GOLD R63.97
Documentation Revision: Phase 2B Enterprise Detail Expansion