Appliance product data keeps changing after refrigerators, washers, dishwashers, and other products go live in your catalog. Manufacturers adjust pricing, release new models, and probably discontinue old ones. Every system that holds the product record, from your website to your Point of Sale (POS) and Enterprise Resource Planning (ERP) software, needs a way to find out about those changes. 

Missing the product data update can leave outdated specs, prices, or models in front of shoppers, which we break down in What Happens When Product Data Changes After You Publish It?. Many systems detect changes by asking for the data repeatedly on a schedule. Most of those checks return nothing new, and an update that lands right after one check has to wait until the next.

Appliance webhooks reverse that direction. When a supported change happens, the data source sends the update directly to an address your system registered, along with change-related data. Your system then decides whether to apply it, review it first, or route it through an existing workflow.

Here's how that process works, from the moment a product changes to the moment your system acts on the update.

How an Appliance Webhook Works

An appliance webhook connects two systems: the source that holds the product data and the software your business uses to manage its catalog. Your system provides a web address to receive updates, then chooses which changes it wants, such as new products, pricing changes, or product status updates.

From there, the data source monitors for changes. When a supported change happens, the data source sends the update to that address, and your system takes it from there. Every update follows the same path, whether it's a new price, a status change, or a new appliance. 

Take a refrigerator that's been in your catalog for months as an example. The listing looks fine, but the manufacturer has just lowered its Minimum Advertised Price (MAP). If your website keeps showing the old price, shoppers may assume your store is more expensive and buy somewhere else.

Here's how that pricing update reaches your system:

1. The product data changes: The manufacturer lowers the refrigerator's MAP.

2. The data source processes the change: Your product data provider picks up the new price and recognizes it as a supported webhook event, in this case, a pricing update.

3. The update is sent to your registered URL: The data source delivers the webhook event to the web address your system provided.

4. Your system receives the payload: The update arrives with the new pricing details, ready to be processed.

5. Your business decides what happens next: Your system can publish the new MAP right away, hold it for review, or route it through an existing pricing workflow.

In the refrigerator example, the new MAP went straight to your software, not to someone's inbox. Who receives each update, and what happens after it arrives, depends on how your business sets up its system.

Send Appliance Data Updates Wherever You Need Them

A webhook update first arrives at the web address your system provided. From there, your business decides where the update goes next and who needs to know. The update can go to whichever system manages your product data, such as your eCommerce website, POS, or ERP. If you work with a software provider, that provider can receive the updates for you.

Some updates only need to reach your software. Others need a person to see them. Your system can turn an update into an alert and send it wherever your team already works, including:

• Email: The catalog manager gets an email when a refrigerator's MAP drops, so they can check the website price before shoppers start comparing.

• Messenger: The sales team sees a channel message (Slack, Microsoft Teams, or others) when a new appliance model becomes available, so they can answer shopper questions before the listing goes live.

• POS alert: Sales staff see a flag on the POS screen when an appliance’s price changes, so the in-store quote matches the website.

You should be able to set where each alert goes, and whether anyone gets one at all. Every alert starts with a supported change, so it helps to know which appliance changes can trigger a webhook.

Choose Which Appliance Updates to Receive

A webhook sends an update when a supported change happens, and each change type is called an event. When you set up a webhook, you choose which events your system receives, then decide how each one is handled:

• New products: A manufacturer releases a new model. Your system can create a draft listing, so the product is ready to review before shoppers start asking for it.

• Product updates: General product information changes, such as the name, color, category, or description. Your system can refresh the listing so the website and POS show the same information.

• Pricing changes: The MAP or Manufacturer's Suggested Retail Price (MSRP) changes, or a promotional price starts or ends. Your system can publish the new price right away or send it to whoever manages pricing.

• Product status changes: A product moves from Coming Soon to Active, or from Active to Discontinued. Your system can open the product for sale at launch, or label a discontinued product so shoppers know it's available only while stock lasts.

• Deleted products: Your product data provider stops supplying data for a product, either for one model or for a whole brand. Your system can flag the listing so your team can decide what to do next.

Not every update needs the same level of care. A new promotional price can go live automatically, while a discontinued product may need someone to check whether the remaining stock covers its open orders. Those rules depend on which events you receive, and supported events may vary by product data provider. 

When your product data and webhook events come from the same provider, it's easier to see which updates are available. From there, you can plan your rules around those updates.

Run Your Appliance Webhooks with Skulytics

Keeping appliance product data up to date shouldn't depend on your team checking manufacturer websites or on your software checking thousands of records that haven't changed. A product data provider like Skulytics can handle that monitoring for you.

Your system loads the catalog through the Skulytics Product Data API, with structured data from more than 400 brands. Skulytics checks each brand's product data on a schedule that varies by brand. When it detects a supported change, such as a lower MAP or a newly discontinued model, webhooks send the update to your system, so your team doesn't have to keep checking. You choose which events to receive, and your business still decides how to handle each update.

Webhooks are included in every Skulytics plan, starting at $100 per month, and you can start with a 14-day free trial. Explore the Skulytics plan or contact the Skulytics team to find the right setup for your appliance catalog.