Reference · built on requestOperator by FibricOrders & fulfillment

Weather Hold

Checks National Weather Service alerts at each perishable order's destination and proposes a hold, a later ship date, or a faster service.

Request accessPricing ↗

About

A perishable order shipped into a storm arrives spoiled or not at all. Weather Hold reads active alerts from the National Weather Service for the county each open perishable order ships to. It maps the destination ZIP code to a county through the HUD USPS ZIP Code Crosswalk and checks that county zone against alerts by event, severity, and ends time. It also reads the carrier's published service alerts and the transit time between origin and destination.

For each affected order it drafts one proposal: hold the fulfillment order, move its ship date past the alert, or step up to a faster service so the package lands before the weather does. You approve, and the operator records the alert, the order, and the change.

This is a reference listing. It documents what Fibric would read from Weather Hold and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Active watches, warnings, and advisories from api.weather.gov/alerts/active by point or county zone, with event, severity, urgency, certainty, onset, and ends
  • The destination ZIP code on each open order, mapped to a county through the HUD USPS ZIP Code Crosswalk's zip-county query
  • Open Shopify fulfillment orders for products you tag as perishable, with their current holds and fulfillAt time
  • Orders awaiting shipment in ShipStation with carrierCode, serviceCode, and shipDate
  • FedEx service alerts as FedEx publishes them on its service alerts page and by email subscription
  • Time In Transit estimates from UPS and transit-time commitments from FedEx for the origin and destination pair

Proposed actions

  • Target capability: propose a Shopify hold through fulfillmentOrderHold with a reason, reasonNotes naming the alert, and notifyMerchant
  • Target capability: propose releasing that hold through fulfillmentOrderReleaseHold by holdIds once the alert's ends time has passed
  • Target capability: propose a new ship date through fulfillmentOrderReschedule in Shopify or POST /orders/holduntil in ShipStation
  • Target capability: propose a faster serviceCode on the ShipStation order before the label is bought
  • Target capability: propose a customer message explaining the delay, sent through your support or messaging connector

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold frozen goods ahead of a winter storm

    When a Winter Storm Warning covers the destination county, propose a hold on the perishable fulfillment order with the alert named in reasonNotes, and a release when the warning's ends time passes.

    With Weather & Severe Alerts, Shopify

  • Shift the ship date around a hurricane

    For orders bound for a county under a Hurricane Warning, propose holduntil the day after the alert ends, so no label is bought for a route the carrier will not run.

    With Weather & Severe Alerts, ShipStation

  • Upgrade the service when the window is tight

    When the UPS or FedEx transit time no longer lands the package before an Excessive Heat Warning begins, propose the next faster serviceCode on the ShipStation order for you to approve.

    With ShipStation, UPS, FedEx

  • Map ZIP codes to alert zones

    The crosswalk turns each destination ZIP into one or more county codes. Each county zone is checked against active alerts, so a ZIP that spans two counties is checked against both.

    With HUD USPS ZIP Code Crosswalk API, Weather & Severe Alerts

Requirements

  • A storefront or shipping connector that exposes open orders with a destination ZIP code and a hold or ship-date control
  • A way to mark which products are perishable: a product tag, a metafield, or a SKU list you maintain
  • A free HUD USPS ZIP Code Crosswalk access token for the zip-county mapping
  • A User-Agent string for api.weather.gov, such as an application name and contact address
Authentication
Alerts from api.weather.gov need only a User-Agent header identifying your application. The HUD crosswalk needs a free access token. Your storefront and shipping connectors use their own credentials as their listings describe.

Limits

  • The National Weather Service feed covers the United States and its territories; destinations elsewhere need a different weather signal
  • Carrier service alerts are published as web pages and email notices, not through an API, so they are read as text and may lag
  • Shopify allows an app up to 10 active holds per fulfillment order; the operator releases its own hold before placing another
  • The NWS rate limit is not published; a refused request is retried after the limit clears, typically within 5 seconds

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Weather Hold ↗

Questions and answers

Which alerts trigger a proposal?
You choose the event names and the minimum severity. Each alert carries event, severity, urgency, certainty, onset, and ends. A proposal names the alert and links to it. Only alerts with status Actual are considered; Test and Exercise messages are ignored.
What does a person approve and what is recorded?
One proposal per order: a hold, a new ship date, or a service change, with the alert that caused it. You approve or dismiss. The record keeps the alert id, the order, the call made, who approved it, when, and how to reverse it.
Does it ever hold or reship an order by itself?
No. It watches alerts and drafts proposals. It never changes an address, cancels an order, or buys a label. Releasing a hold is also a proposal, raised when the alert's ends time passes. Orders without a perishable item are not touched.
Ask about Weather Hold

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy