Review a Foundry catalog and buyer request
Check published catalog facts, inspect a request, and separate internal notes from buyer-visible responses.
Foundry OMS brings catalog facts and buyer requests into a reviewed commerce workflow. It is in controlled rollout/early access, so the destinations and actions available to your account depend on its configuration and your permissions.
For Northgate ESD Packaging, imagine a buyer asking for custom protective inserts. The operator needs to confirm the requested product and requirements before accepting or forwarding work.
Check the catalog before the request
- Select the Northgate demo account.
- Open Foundry OMS > Catalog.
- Find the intended product.
- Read Source, Publication, and any Source Review Required notice.
- Inspect the product facts and available capabilities.
A draft product stays private until reviewed and published. Product capabilities can narrow what the business listing permits; they cannot independently activate a business capability that is unavailable.
If you manage catalog publication, use Preview & Publish and read the proposed snapshot before choosing Publish Reviewed Fields. Saving a draft does not update the public snapshot. Check the publication state after the action rather than assuming the edited facts are already visible to buyers.
For Northgate, verify approved dimensions, application notes, and quote requirements. Do not turn a source-review warning into an invented availability or delivery promise.
Inspect the incoming request
- Open Requests or Orders, according to the item you need to review.
- Open its detail view.
- Read the buyer, needed-by information, and external reference.
- Inspect Requirements / Project Brief and Requested Lines.
- Read History & Buyer Messages before deciding on a response.
Check quantities and notes together. “Two hundred inserts” is incomplete if the dimensions or intended equipment are unknown. The request's current state and history also help you avoid treating an already reviewed item as new work.
An imported store receipt or external reference provides context about the source. It does not automatically grant Forge authority to change every downstream status. Available actions depend on the item's lifecycle and ownership.
Respond in the right place
Use Review & Respond when the detail view offers it. Buyer-Visible Message is shown in the buyer's authenticated request status. Internal Notes is for the operating team.
- Enter a clear buyer-facing question when information is missing.
- Add internal context in Internal Notes if needed.
- To ask for missing information, leave the question in the message field and choose Request Information directly.
- Read the status confirmation and enter the internal reason.
- Confirm the updated history and status.
To save a response without changing the lifecycle, use Save Response / Notes instead. A successful save clears the message field. If you save first and later choose Request Information, enter a new buyer-visible question before taking that action. For Accept Request or another available status action, review the intended transition and reason before confirming.
Request Information requires a buyer-visible question. The status-change reason is recorded internally; it does not substitute for the message the buyer needs to read.
Note: Saving a buyer-visible message here does not send an email. Buyers see it in their authenticated request status.
Verify the next handoff
Accepting a request is not the same as completing fulfillment. If the workflow includes a destination mapping, delivery review, or external system, inspect that next stage and its result separately. Do not infer an external order from a local status label alone.
If a button is missing, first check the current state and source ownership. Not every lifecycle transition is available for every request. If access is unavailable, the account's Forge operator can confirm rollout eligibility and permissions.
Completion means the reviewed catalog information and request decision are clear, the buyer can see the intended response, and any remaining downstream work has an identified owner.