Custom code fragmentation
Default WooCommerce behavior does not cover optical-specific constraints without substantial custom code.
Technical implementation
WooCommerce left and right eye cart configuration
Configure WooCommerce left and right eye cart behavior so each eye can carry unique prescription values and quantities.
Designed for agencies and developers who need predictable behavior across product, cart, checkout, and orders.
- Server-side validation
- Native WooCommerce hooks
- Zero custom SQL
Common blockers this page solves
Data model inconsistency
Independent custom snippets per store create maintenance overhead and inconsistent data structures.
Maintenance overhead
Order metadata quality degrades when cart logic and field validation are implemented in disconnected layers.
Implementation plan
- Phase 1: Define one canonical data model for prescription fields, conditions, and valid ranges by product family.
- Phase 2: Apply the same validation logic in product UI, add-to-cart, and server-side order creation.
- Phase 3: Connect pricing and stock rules to the same logic layer to avoid drift in production.
- Phase 4: Validate output in WooCommerce admin and exports, then lock changes behind staging-first release checks.
What WP Optix adds for this use case
Prescription and validation layer
- Field-level controls for sphere, cylinder, axis, BC, DIA, and add power.
- Conditional logic and valid-range enforcement by product family.
- Consistent prescription data from product page to order metadata.
Commerce and operations layer
- Dual-eye cart items with independent quantities and predictable fulfillment data.
- Dynamic pricing by box count and lens type.
- Compatibility with modern WooCommerce architecture including HPOS.
Expected outcomes
Business outcome
Cleaner and more reliable order metadata.
Operational outcome
Lower long-term technical debt for agency-managed stores.
Scalability outcome
Safer upgrades with HPOS and WooCommerce releases.
Pricing and next steps
WP Optix plans are currently available from USD 79/year to USD 299/year, based on store scale and team needs.
Use pricing for direct purchase decisions and book a demo when you need help mapping catalog rules, validation logic, and rollout sequence.
Frequently asked questions
Why not use one variation line for both eyes?
Single-line models are error-prone. Separate eye entities preserve clarity and reduce fulfillment mistakes.
Can each eye have different subscription cadence?
Yes. WP Optix supports independent quantity and cadence logic by eye.
How is this stored in WooCommerce orders?
Each eye configuration is retained in structured line item metadata for downstream workflows.