User Documentation: WebMe Temporal Cart Controller
Table of Contents
- Installation
- Setup
- Workflows
- Troubleshooting
- FAQ
Installation
- Install and activate WooCommerce.
- Install and activate WebMe Temporal Cart Controller.
- Open WooCommerce > Order Windows.
Setup & Configuration
- Add a new rule or start from a template.
- Set the rule label and priority.
- Choose scope:
- Storewide
- Products
- Categories
- Tags
- Enter scope IDs when scope is not storewide.
- Enter weekly windows using
HH:MM-HH:MMranges separated by commas. - Add blackout ranges as
YYYY-MM-DD|YYYY-MM-DDorYYYY-MM-DD HH:MM|YYYY-MM-DD HH:MM. - Choose enforcement:
- Add to cart
- Checkout
- Both
- Set optional closed button text and customer message.
- Save rules.
Common Workflows
-
Storewide business hours
- Use the Weekly ordering hours template.
- Keep scope as storewide.
- Enter open hours for each weekday.
-
Timed product drop
- Use the Product drop window template.
- Change scope to products and add the product ID.
- Set the weekly window for the drop period.
-
Holiday closure
- Use the Holiday blackout template.
- Keep all-day weekly windows.
- Add the date blackout range that should override normal ordering.
-
Category pause
- Use the Category closed period template.
- Enter category IDs.
- Add blackout dates or keep an always-open weekly window if only blackout periods should block ordering.
Troubleshooting
-
Rules do not match expected products
Confirm scope type and numeric scope IDs. Product rules also consider parent product IDs for variations. -
Customers can still add to cart
Confirm the rule is enabled and enforcement includesadd_to_cart. -
Customers reach checkout before the rule triggers
Confirm enforcement includescheckout. -
No future reopening time appears
This happens when a rule has no upcoming valid transition inside the current rule definition. -
Overnight windows do not work
Weekly windows require same-day ranges where end time is later than start time.
FAQ
Scale & Performance
- Q: Will this add heavy database load?
A: No custom tables or background jobs are used. Runtime reads one option payload and evaluates it in PHP during product, cart, and checkout flows.
Data & Footprint
- Q: What data does the plugin store?
A: One option namedwebme_tcc_rulescontaining sanitized rule definitions.
Lifecycle & Uninstallation
- Q: What happens if I uninstall the plugin?
A: Current codebase does not include an uninstall routine, so stored rule data is expected to remain unless removed manually.
Compatibility & Conflicts
-
Q: Does this require another service?
A: No. It depends on WooCommerce only. -
Q: Is HPOS supported?
A: Yes. The plugin declares HPOS compatibility, although it does not create or manage order records itself.
Best Practices
- Keep priorities simple and documented for store staff.
- Use preview before saving large rule changes.
- Prefer product/category/tag rules only when storewide rules are too broad.
- Keep customer-facing closed messages explicit about reopening time.