XSTIX

Featured Case Study

Custom E-Commerce · WordPress Development · Data Integration · Payment Workflow

XSTIX needed an online ordering system built around the way the business actually operates, not around the assumptions of a conventional shopping-cart platform. Amixa designed and developed a purpose-built commerce application that combines a constrained hockey-stick configurator, custom cart and checkout workflow, spreadsheet-driven catalog synchronization, shared blade-pattern artwork, and a Venmo payment handoff.

Project Overview

Most e-commerce systems begin with a standard model: choose a product, select a quantity, pay through an integrated card processor, and ship from inventory. XSTIX works differently. Hockey sticks are sold as specific combinations of manufacturer/model, hand, flex, blade pattern, and color/finish. Supplier availability changes over time, orders are coordinated around pickup, and payment is handed off to Venmo after the order is created.

A stock commerce package could have exposed hundreds of near-duplicate variants while still leaving the business with significant manual catalog maintenance. Amixa instead treated XSTIX as a custom application project, using WordPress as the content and administration foundation while building the ordering and data workflows specifically for the business.

The Core Requirement

The central design problem was straightforward to describe but nontrivial to implement:

Make a complex configuration matrix feel simple to the customer, while making recurring supplier inventory updates simple and safe for the administrator.

Purpose-Built Product Configurator

A stick is not presented as a flat list of hundreds of separate SKUs. Customers begin with the product they want and select the configuration dimensions that matter:

• Manufacturer and model
• Hand
• Flex
• Blade pattern / curve
• Color / finish

The public selector operates as a bidirectional constraint solver. Every selection is evaluated against the actual configuration matrix. If a customer chooses a value that makes another option impossible, the unavailable option is disabled immediately. The same logic works in either direction: selecting a blade pattern can constrain flex choices just as selecting a flex can constrain blade-pattern choices.

This keeps all relevant choices visible while preventing combinations that do not exist in the supplier data.

A Custom Shopping Cart

The XSTIX cart was developed around configurations rather than generic product IDs alone. Each line preserves the exact combination selected by the customer, along with the applicable backup preference.

The cart therefore represents a requested configuration, not an unconditional promise that a saved selection can still be ordered indefinitely.

Checkout Revalidation

Catalog availability can change between the time a customer adds a stick to the cart and the time checkout is completed. XSTIX does not blindly trust stale cart state. The primary selection and any different-stick backup configuration are revalidated at checkout against the current availability matrix.

If a later spreadsheet import removed a saved choice, checkout stops the stale order and sends the customer back to review the cart. Completed orders, by contrast, retain immutable snapshots of what was ordered.

Spreadsheet-Driven Inventory

The business already receives structured availability data in Excel workbooks. Rather than asking an administrator to manually reproduce that data in WordPress, Amixa built a repeatable XLSX import workflow around the existing business process.

The spreadsheet is authoritative for the configuration matrix. Current imports can define manufacturer, model, hand, flex, blade pattern, and color/finish availability. The application translates that structured source data into customer-selectable combinations.

Preview Before Apply

Inventory synchronization is intentionally a two-stage process:

1. Upload and Preview. Parse the workbook, map products, calculate changes, surface warnings, and show what would be created, reactivated, deactivated, added, or removed. The live catalog is not changed.
2. Review and Apply. Only after the preview is accepted does the administrator explicitly apply the import.

Ambiguous mappings block Apply rather than forcing the importer to guess.

Idempotent Monthly Synchronization

The importer is designed for recurring supplier workbooks. An unchanged workbook does not delete and recreate the catalog. Stable stick and blade-pattern records retain their identities, and administrator-maintained content such as pricing, descriptions, product imagery, and blade artwork is preserved.

That distinction is important: the spreadsheet owns availability, while WordPress can continue to own the merchandising content that does not belong in the supplier feed.

Product Lifecycle Instead of Destructive Deletes

If an imported configuration disappears from a later workbook, it is removed from online availability. If a spreadsheet-managed model disappears, it can become inventory-inactive rather than being deleted. If it reappears later, it can be reactivated. Newly discovered products enter in a controlled, non-orderable state until their store content is complete.

The system therefore separates two questions:

• Does this product/configuration exist in the current supplier data?
• Has the administrator approved it for customer ordering?

Blade Pattern Visualization

Blade curves are an important part of selecting a hockey stick, so XSTIX includes dedicated blade-pattern artwork and an image viewer inside the ordering experience.

The artwork model is intentionally normalized. A blade image belongs to one manufacturer + pattern identity and is reused by every matching stick and by both hand configurations. Administrators can select an existing cropped image or create a new crop from source artwork when needed. That avoids maintaining duplicate images for every product variant.

Guest Checkout Built for the Workflow

XSTIX deliberately avoids customer accounts and unnecessary checkout friction. A shopper can complete an order without creating a login, password, or customer-facing order-history account.

The checkout collects the information the business actually needs:

• First and last name
• Mobile phone number
• Pickup location
• Optional referral information
• Order confirmation
• Cloudflare Turnstile validation

Backup Preference

Special-order products introduce an operational question: what should happen if the requested stick becomes unavailable? XSTIX captures that preference during ordering. Customers can choose to wait for the requested configuration or permit XSTIX to work with them on a different stick.

A different-stick backup is itself validated as a real, currently orderable configuration instead of being stored as unstructured text.

Venmo Payment Handoff

XSTIX did not need a conventional embedded card gateway. It needed a clean transition from a confirmed website order to the business’s Venmo payment process.

After checkout succeeds, the order is saved first. The confirmation page can then display:

• The order number and total
• The ordered stick configurations
• A configured Venmo QR code
• A direct Pay for your order now link

Both the Venmo URL and QR image are managed from WordPress. More importantly, the configured payment target is snapshotted onto each new order. If an administrator later changes the global Venmo settings, the payment information associated with an existing order does not silently change underneath the customer.

The integration is intentionally a payment handoff, not a false simulation of a payment processor. XSTIX records the order; Venmo handles the payment transaction. The website does not claim to verify Venmo settlement status.

Administration Designed for Repeated Use

The back end is purpose-built around the tasks XSTIX actually performs:

• Inventory workbook Preview and Apply
• Stick merchandising and orderable state
• Manufacturer-specific blade patterns and reusable artwork
• Orders and referral information
• Pickup workflow
• Venmo payment settings

Generic commerce controls that do not fit the operating model are kept out of the critical path. The objective is not to expose every possible setting; it is to expose the right settings.

Security and Transaction Boundaries

Public checkout is protected with Cloudflare Turnstile and server-side validation. Transaction-critical state is checked again on the server instead of trusting browser selections alone. The same defensive approach is used for stale-cart validation and controlled inventory imports: external or previously stored input is validated at the point where it can affect an order or the live catalog.

What Looks Simple – and What Happens Underneath

Supplier Spreadsheet → Import Preview → Catalog Matrix → Customer Configurator → Cart Revalidation → Order Snapshot → Venmo Handoff

The customer sees a focused ordering interface. Underneath it, the application coordinates supplier data, product identity, allowed configurations, administrative merchandising, cart state, checkout validation, order snapshots, and external payment instructions.

Architecture

Why Custom Development Mattered

XSTIX is a practical example of when custom development provides more value than forcing an unusual business process into a generic commerce platform. The project did not need every feature of a large online store. It needed a smaller set of capabilities to model the business precisely:

• Represent a complex hockey-stick configuration matrix accurately.
• Make that matrix easy for customers to navigate.
• Synchronize changing supplier availability from spreadsheets.
• Preserve administrator-managed product content across repeated imports.
• Prevent stale cart selections from becoming invalid orders.
• Capture only the checkout information the business needs.
• Hand payment cleanly to Venmo without pretending Venmo is an embedded gateway.

The Result

XSTIX now has a storefront whose customer-facing simplicity hides a substantially more sophisticated application underneath. Customers get an intuitive ordering flow. Administrators get a repeatable catalog-synchronization process built around the supplier workbook. The business gets software that follows its real operating model rather than requiring the business to conform to a generic shopping-cart package.

Technology & Capabilities

Custom WordPress development; purpose-built e-commerce; PHP; JavaScript; XLSX data integration; configuration constraint solving; custom cart and checkout; catalog synchronization; WordPress Media Library integration; Venmo payment handoff; Cloudflare Turnstile; managed hosting and deployment.

Related Amixa Services

Visit XSTIX · Custom Web Applications · WordPress Development · Discuss a Project