I plan to use Busabase to manage product data and have agents periodically update descriptions and prices. While content adjustments matter, I am more concerned with whether the price has been changed. Could "price" be designated as a key field during the review process and highlighted in the pending review list? If this isn't currently supported, I would like to request this feature to facilitate priority checks.
Thanks for explaining why a price edit needs more attention than a description edit. In Busabase, opening a Change Request shows the changed fields and their before/after values. The pending-review list cannot currently mark price as a special field or highlight every request that changes it.
For now, ask the agent to submit price changes separately from copy edits and say “price change” with the old and proposed prices in the request description. Keep price edits behind human review; a description-only request should not hide one. We have recorded the list-level highlight request, with no design or release date committed. Would a price-change badge in the queue be enough, or should changing price also require a separate confirmation before approval?
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in