Strategy Playground
A safe place to write pricing rules down, see where they conflict, and understand what they would do.
Inputs
What data is required?
- Pricing rules, floors, ceilings and exceptions written in plain terms
- A set of rates to run the rules against
Outputs
What does it calculate, display or help you decide?
- The rules that would apply to each rate, and in what order
- Every conflict between rules, shown rather than silently resolved
Build prompt
Not yet written. This module is proposed and not scheduled. The purpose, inputs, outputs and operating complication above describe what it would do; the build prompt, setup steps, dependencies and tests will be added if it is taken forward.
The part that catches people out
Rule conflicts, floors and ceilings. Rules written at different times stop agreeing with each other. A floor set for one class can contradict a ceiling set for a location, and the result depends entirely on the order the rules are evaluated in. A playground earns its place by making the conflict visible before it reaches a live rate.
Optional RME connection
RateMonitor Elite remains the pricing engine where an operator uses it. A playground is a place to reason about rules, not a route to publishing them.
Any connection to RateHighway services would require approved interfaces, authorisation, tenant isolation and verified data rights. Nothing about access or availability is approved.
Proposed, not scheduled
There is nothing to build from yet. Start with a module that has a written prompt, or read the playbook to decide whether this one is worth building at all.