When several products share a price structure, repeated manual edits become difficult to maintain. A shared rule can reduce that work, provided the school knows exactly which offers it affects.
Group by the rule, not just the product name
Identify offers with the same duration, seasonal or category logic. Two boards may share one rental price category while remaining separate physical items. Conversely, similarly named courses may need different pricing because their delivery or inclusions differ.
TIDEFORCE Pricing Models support reusable price structures. Rental price categories apply the same principle to groups of rental items. Staff decide the rules; this is not a promise of automatic demand-based price optimization.
Test boundary cases before changing prices
Try a representative date, a season boundary and the important durations or quantities. Check the final customer total and how included items or extras appear. Compare the result with the intended offer rather than only checking that a setting was saved.
Use supported preview views where available. A price rule does not guarantee that every external website has refreshed its displayed price; check the connected customer route separately.
Assign ongoing ownership
Keep a person responsible for seasonal updates and exceptions. When an offer should no longer follow a shared rule, review the relationship before editing the rule for everyone else.
These are prices charged by the school to its guests. They are distinct from TIDEFORCE's platform fees and Website Sync API usage charges. Those commercial terms belong on the pricing page and Website Sync page.
See pricing and capacity for the product workflow.
How does this work at your school?
Bring an everyday task from your school. We’ll show you how it could work in TIDEFORCE.
Request a demo →