Athenian Point of Sale for WooCommerce
Overview
Product overview
WooCommerce is strong at online storefront transactions, but in-person selling introduces different operational needs. Staff need a focused register view, rapid product search, fast ticket building, simple payment-state capture, operator accountability, location and station context, and a clean way to distinguish POS orders from standard ecommerce traffic.
ATHPOS solves that by layering a purpose-built point-of-sale workflow on top of WooCommerce. It lets merchants run a shortcode-driven register, restrict access to approved staff, assign operators to registers or stations, capture order context such as service mode and payment method, support configurable items and manual price overrides, and report on POS-origin sales separately from the rest of the store.
Use cases
- In-person sales
- Retail operations
- Store checkout
- Order capture
Developer
Developer starting point
This baseline documents the POS implementation and WooCommerce seams. It does not claim that a live sale, payment, inventory change, receipt, or device interaction has been exercised.
Ecosystem integration story
WooCommerce
ATHPOS is built directly on WooCommerce products, orders, taxes, order statuses, and admin order management. It uses WooCommerce as the commerce engine while providing a more operationally efficient front-end for in-person order entry.
WordPress shortcode-driven deployment
ATHPOS is deployed through the [athenian_pos] shortcode, allowing merchants to place the register on a private page, kiosk page, or internal service screen without building a separate application stack.
Athenian Product Add-ons
If Athenian Product Add-ons is active, ATHPOS can surface add-on groups inside its item configuration flow, recalculate line totals with add-on adjustments, and persist that add-on context to WooCommerce order items. This extends the register beyond simple SKU tapping into configurable in-person selling.
Operator and staff workflows
ATHPOS integrates with WordPress roles and capabilities so administrators, shop managers, and designated support or service users can be granted register access, reporting visibility, and assignment management according to operational need.
Reporting and store operations
Because ATHPOS tags POS-origin orders distinctly, it can provide a cleaner operational lens for managers who need to separate front-counter activity from normal web checkout activity while still keeping all transactions inside WooCommerce.
Install
- Reviewed source folder: athenian-point-of-sale
- Plugin version reviewed: 0.1.0
- Local source inventory: 17 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-point-of-sale at baseline/devdocs-0.1.0-20261006e / 590f5719891e7e584bda6781565dc77244012661.
- WordPress and WooCommerce.
- Payment, inventory, customer, order, receipt, and device effects require separate authenticated target verification.
Configuration
- Working positioning — see the linked technical reference excerpt.
- Executive summary — see the linked technical reference excerpt.
- Core marketing message — see the linked technical reference excerpt.
- The problem ATHPOS solves — see the linked technical reference excerpt.
- What ATHPOS does — see the linked technical reference excerpt.
- Ecosystem integration story — see the linked technical reference excerpt.
- Why this matters commercially — see the linked technical reference excerpt.
- Key differentiators — see the linked technical reference excerpt.
- Suggested messaging pillars — see the linked technical reference excerpt.
- Short-form copy options — see the linked technical reference excerpt.
- Sales narrative — see the linked technical reference excerpt.
- Best-fit use cases — see the linked technical reference excerpt.
- Positioning statement — see the linked technical reference excerpt.
- Platform-focused primary functionality copy — see the linked technical reference excerpt.
Usage
- Shortcodes detected in local PHP source: 1
- Static action/filter hooks detected in local PHP source: 12
- REST route registrations detected in local PHP source: 0
Shortcodes
- athenian_pos — includes/class-athpos-shortcode.php
REST Endpoints
- No register_rest_route calls were detected by the baseline scanner.
Hooks
- admin_enqueue_scripts — includes/class-athpos-assets.php
- admin_menu — includes/admin/class-athpos-admin.php
- admin_notices — athenian-point-of-sale.php
- admin_post_athpos_save_assignments — includes/admin/class-athpos-admin.php
- admin_post_athpos_save_settings — includes/admin/class-athpos-admin.php
- before_woocommerce_init — athenian-point-of-sale.php
- init — includes/class-athpos-assignments.php
- init — includes/class-athpos-settings.php
- plugins_loaded — athenian-point-of-sale.php
- wp_ajax_nopriv_ — includes/class-athpos-ajax.php
- wp_ajax_ — includes/class-athpos-ajax.php
- wp_enqueue_scripts — includes/class-athpos-assets.php
Data Model
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: 3680a9c2dd57144f7bb6ed002a01df94e8627c396e5a45c81c1d0ad522b18a0e
- Repository URL: https://github.com/Athenian-Brands/athenian-point-of-sale
- Repository reference: baseline/devdocs-0.1.0-20261006e
- Repository commit: 590f5719891e7e584bda6781565dc77244012661
Source files include: assets/css/athpos-admin.css, assets/css/athpos-app.css, assets/js/athpos-app.js, athenian-point-of-sale-icon.png, athenian-point-of-sale.php, athenian-point-of-sale.zip, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/athpos-marketing-document.md, docs/technical-marketing.md, includes/admin/class-athpos-admin.php, includes/class-athpos-ajax.php, includes/class-athpos-assets.php, includes/class-athpos-assignments.php, includes/class-athpos-reports.php, includes/class-athpos-settings.php, includes/class-athpos-shortcode.php
Troubleshooting
This baseline documents the POS implementation and WooCommerce seams. It does not claim that a live sale, payment, inventory change, receipt, or device interaction has been exercised.
- Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.
FAQ
What is this page intended to establish?
A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.
Is the linked repository baseline verified?
Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.
What remains for release-grade documentation?
Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.