Change Management Post-Approval

This article explains what happens to the Cost Submission if there is a specification or cost change to the product after the approval has been made.

There are three types of specification change that can occur on Loupe after a Cost Approval is made:

• Direct change to the declared cost or specification in the Cost Submission by the Vendor of Record
• Change to the underlying specification of the product by the Vendor of Record

Any of these changes will cause the Cost Submission to enter a withdrawn state. The vendor now needs to resubmit for approval. During the withdrawn state the retailer cannot see any data:

After the supplier resubmits the cost Submission you will need to start the process over and re-approve the Cost Submission.

How do we know what has changed when a Cost Submission is resubmitted?

When a Cost Submission is changed, the change will always be captured in the Activity Log which is visible to both buyer and supplier, serving as a single source of truth for both.

What happens to the Linesheet FOB Cost when CS is withdrawn?

The FOB on your Linesheet will behave differently in this scenario as a function of whether or not the product has ever been approved.

• If the product has previously been approved (and therefore could already carry a SKU) then the price will display the previously approved Total Cost (the vendor quote) adjusted to the metal lock(s) the buyer has saved for the product in question
• If the product has not previously been approved (and therefore cannot already carry a SKU) then the price will revert to the supplier's showroom quote price (the vendor quote before the Cost Submission started) adjusted to the metal lock(s) the buyer has saved for the product in question

What happens to Purchase Orders while Cost Submission is withdrawn or not yet approved?  

The way your purchase orders will interact with Cost Submission depends on if you are using the Loupe purchase order system or a 3rd party purchase order system.

• Loupe purchase order system will not allow a PO to be cut for an Enterprise product that does not carry Sourcing Approval
• 3rd party purchase order system will depend on the logic your Integration team has in place with their configuration of exports from Loupe.
  • Most Enterprise Retailers will seek to implement the same logic as Loupe would natively and prevent the creation of purchase orders for products that do not carry Sourcing Approval
  • Some Enterprise retailers will seek to enable their purchase orders to continue to be issued at the most recently approved Sourcing Cost (this feature is available to Enterprise Integration teams)