What counts as a product change
Product changes are the day to day adjustments that keep a print storefront accurate. That can mean new size options, revised artwork fields, a fresh price matrix, changed proofing steps, extra courier choices or a new user role for a corporate portal.
Small edits often sit inside one job, but they touch several parts of the store. A size change can affect pricing, artwork rules and the way the product displays in the B2B portal, so it helps to send the full picture instead of only one line.
Send the details in the order the shop needs them
Start with the product name and the exact change you want. Then add the fields, options or rules that must stay in place. If you are replacing an old setup, mark what must be removed and what must remain visible to customers or internal staff.
- Product name and category
- New options, sizes, finishes or quantities
- Price matrix notes, including any breaks or set-up fees
- Artwork rules, proofing steps and file checks
- Portal user changes, role changes or access limits
- Delivery zones, collection notes or courier rules
How price matrix updates are handled
Price changes need clean instructions because the same product can price differently by size, material, quantity or print method. If you want tiered pricing, send the breakpoints in a clear table or list. If a price must only appear to logged in corporate users, say that plainly.
We also look for knock-on changes. A revised matrix may need a new minimum order quantity, updated VAT display, or a different rounding rule for line items. If the change affects a quotation display, include the wording you want the customer to see.
Artwork rules and proofing workflow edits
Artwork rules keep file handling predictable. They can cover bleed, safe area, accepted formats, colour requirements, naming rules and what happens when a file fails preflight. Proofing workflows decide when a job pauses, when approval is needed and who sees the next step.
- Tell us if artwork must be uploaded before checkout
- State whether proofing is automatic or manual
- Note who approves, customer or staff
- List any blocking issues that should stop an order
- Include text for error messages where needed
Portal users and access levels
Corporate portals often need user changes without disturbing the full account. A buyer may need place-order access, while a manager needs approval rights and a finance contact only needs statements. Send the full user list with each role clearly marked, especially when one company has branches in different towns.
If a user leaves, specify whether the account must be disabled, reassigned or kept for order history only. That avoids gaps in tracking and keeps the approval trail neat for the client side.
What happens after the brief is received
Once the brief is complete, the change is checked against the current storefront setup, template structure and workflow rules. Related settings are adjusted together so a pricing edit does not clash with checkout logic or a portal permission. If supporting files are needed, such as artwork samples or a pricing sheet, include them with the request.
When the update is ready, it can be reviewed in the store environment before it is moved into active use. That is the point where product builders, proofing steps and delivery settings are checked as one chain, not as separate pieces.
Useful details to include the first time
A complete brief saves back and forth in the admin area and helps avoid mismatched settings between products. Keep the wording direct and use the same terms your team uses in the shop.
- Product name exactly as it appears in the storefront
- Short note on the reason for the change
- Any old option that must be retired
- Preferred customer-facing wording
- Branch or client group affected, if the rule is not for everyone
When a workflow review is the better call
Some changes are not just edits to one product. If your pricing, proofing and fulfilment steps no longer match how the shop runs, a workflow review is the better starting point. That is useful when a single product has grown into several variants, or when portal users are following different steps for the same item.
In those cases, the update should be planned across the catalogue, payment step and delivery handoff. It keeps the customer path clear and reduces manual fixing inside the order queue.
