Reference · built on requestOperator by FibricOrders & fulfillment

Holiday Cutoff

Reads carrier transit times, holiday calendars, and where your orders go, then proposes last-order dates per service and flags late orders.

Request accessPricing ↗

About

Every holiday has a last day an order can be placed and still arrive, and it differs by service and by region. Holiday Cutoff reads the carrier's transit figures for each lane you ship, the public holiday calendar for the destination countries, and your warehouse's own cutoff time and non-shipping days.

It proposes a table of last-order dates per service and region for a named holiday, the copy that publishes them, and, once the dates pass, a flag on each order placed too late with an offer of the upgrade that still arrives in time. A person approves the table and each hold. The table keeps its inputs, and every flagged order keeps the offer and the answer.

This is a reference listing. It documents what Fibric would read from Holiday Cutoff 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

  • UPS Time in Transit for each origin and destination pair and service: businessTransitDays, deliveryDate, and saturdayDeliveryIndicator
  • FedEx transit times per service from the Rates and Transit Times API with returnTransitTimes set
  • Public holidays by country from Nager.Date, with holidayTypes, nationalHoliday, and subdivisionCodes, and by subdivision from OpenHolidays
  • Where your orders go: destination postal codes and countries from recent Shopify orders, grouped by ship-from location
  • Your fulfillment cutoff time per location and the days the warehouse does not ship
  • Incoming orders compared with the published cutoff for their destination and service

Proposed actions

  • Target capability: propose a table of last-order dates per service and destination region for a named holiday
  • Target capability: propose the storefront and checkout copy that shows the cutoff, for your team to publish
  • Target capability: propose a hold and a message on an order placed after its cutoff, offering an upgrade or a later delivery
  • Target capability: propose a Klaviyo event for customers in a region whose cutoff falls inside the notice period you set
  • Target capability: propose a revised table when a carrier's transit response changes for a lane

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

What you can build

  • Publish one table per holiday

    For a named holiday, propose last-order dates for ground and each express service by region, built from UPS and FedEx transit responses, Nager.Date holidays, and the warehouse calendar.

    With UPS, FedEx, Holidays & FX Reference

  • Catch the order placed an hour late

    A Shopify order after its regional cutoff, checked against OpenHolidays for the destination subdivision, gets a proposed hold and a message offering the express upgrade that still lands in time.

    With Shopify, OpenHolidays API

  • Warn the regions with the earliest cutoff

    Customers in regions whose cutoff falls inside the notice period get a proposed Klaviyo event, keyed to their Shopify profile, that your reminder flow turns into an email.

    With Klaviyo, Shopify

Requirements

  • Carrier transit time access for the carriers you use: UPS Time in Transit, FedEx Rates and Transit Times
  • A holiday source for the destination countries: Nager.Date, OpenHolidays
  • Your warehouse calendar: cutoff time per location and non-shipping days
  • Order history with destinations, so the table covers the regions you ship to
  • A named owner who publishes cutoff copy and approves order holds
Authentication
OAuth client credentials for UPS and FedEx, a Shopify app token, and a Klaviyo private key; the holiday feeds need no credential.

Limits

  • Transit days are the carrier's estimate for the lane on that ship date; a guaranteed service is the only one with a committed date
  • The holiday feeds list public holidays; carrier surcharge periods and peak embargoes are not in them and must be entered by you
  • The table is per service and region; an address the carrier cannot serve by the date is flagged rather than dated
  • It flags late orders; it does not upgrade or cancel them without approval

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 Holiday Cutoff ↗

Questions and answers

What does the owner sign off?
The cutoff table for a holiday and, order by order, the hold or upgrade offer for those placed after it. Each table line shows the carrier response, the holidays counted, and the warehouse cutoff it rests on.
What is kept after the holiday?
The published table with its inputs and its approver, and on each flagged order the cutoff it missed, the offer made, the customer's answer, and the time. A revised table keeps the earlier version beside it.
Does it publish or hold anything by itself?
No. Publishing copy, holding an order, changing a service, and sending a reminder are proposals a person approves, and each approved one runs one time. When a carrier returns no transit figure for a lane, that region is listed as unresolved.
Ask about Holiday Cutoff

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