View price changes
MARPLA creates a milestone when a price changes. No manual duplicate is needed.
How to use it
- Open Milestones or a price milestone on a chart. Edits within three hours of the first change are grouped.
- Inside, review each product, its old and new price, and its timestamp. External edits show detection time.
Advice and practical context
Observed change
An automatic milestone stores a known price transition and its time. Edits within three hours are grouped for readability, while individual products and transitions remain inside. External edits carry detection time, which may not be the exact action second.
Avoid duplicate events
A manual copy of the same price change suggests two interventions. Add context about the reason or campaign without replacing the factual record. Do not assume grouped edits were one identical change across every product.
When price changes several times, the duration of each level and its complete days matter. The final price does not describe the path. Inspect milestone details and do not combine a brief mistaken edit with a sustained test window.
Technical detailsCalculations, permissions and behavior
Automatic price milestones
MARPLA automatically creates a milestone when it confirms a product price change or detects one during catalog sync. Changes to products in the same game within three hours of the first change share one milestone. A later change starts a new window; each edit does not extend the existing window.
Each item shows its product, previous and new price, and timestamp to the second. For MARPLA edits this is the Roblox confirmation time; external edits show detection time because their exact application time is unknown. Syncing an unchanged price creates no milestone.
No separate manual milestone is needed. Price history remains complete, and product charts do not duplicate changes already included in a milestone. Automatic price milestones require monetization view permission.