Strawberry can reconcile an approved inventory or cost file against the current product catalogue, identify the items that need attention, and stage a change list for review. A merchant owner should confirm any price or availability change before customers see it.
01
The SKU is the unit of truth, not the product title.
Product titles change, variants multiply, and supplier files rarely match a storefront perfectly. Start with the SKU or another stable identifier, then let Strawberry compare the source file with the current catalogue.
The resulting change list can distinguish an exact match from an item that needs manual mapping.
02
A proposed price should show its calculation inputs.
A new price without a source, cost date, or margin check is difficult to approve.
Strawberry can prepare the proposed value alongside the current price, supplier cost, rounding rule, and any threshold you define.
That makes it possible to review a group of updates quickly without losing the reason behind each one.
03
Stock changes need their own exception lane.
An item being unavailable is not always a reason to remove it from sale.
Some products can be backordered, some should be hidden, and some need a customer-facing date. Strawberry can separate these cases based on the rules you supply.
The final decision belongs to the catalogue owner because it affects demand, revenue, and customer expectations.
04
A good update log makes rollback possible.
For every proposed change, retain the before value, proposed value, source, timestamp, and reviewer. Strawberry can prepare that log as part of the update pass.
Once the workflow is proven, save the reconciliation logic as a skill. Run a routine to prepare a review queue, not to silently publish prices.