Reference · built on requestOperator by FibricOrders & fulfillment

Ship-To Change

Turns an address-change request into an order edit, a carrier intercept, or a decline, depending on where the shipment is.

Request accessPricing ↗

About

Whether an address can still be changed depends on where the package is. This operator reads change requests as they arrive in the help desk, finds the order, and checks the fulfillment order's status and the shipment's tracking state. Before a label exists, it proposes the order edit. After the label but before delivery, it proposes the carrier's intercept: UPS Delivery Intercept with the alternate address request type, or USPS Package Intercept for a commercial sender. Once the package is out for delivery or delivered, it proposes a decline that says so and offers the return or reship path.

A person approves each step. The customer reply, the intercept request, and the carrier's charge are recorded on the ticket and the order.

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

  • Help desk tickets whose message asks to change where an order is going, with the new address the customer typed
  • The Shopify fulfillment order's status (OPEN, IN_PROGRESS, ON_HOLD, CLOSED) and its supportedActions, including HOLD and MOVE
  • Fulfillment displayStatus such as LABEL_PRINTED, IN_TRANSIT, OUT_FOR_DELIVERY, or DELIVERED, and the trackingInfo
  • Intercept eligibility and charges for a UPS tracking number through the Delivery Intercept API
  • ShipStation shipments and labels as they are created or voided, and the order-to-shipment link
  • Shippo tracking status PRE_TRANSIT or TRANSIT and the substatus address_issue on the shipment

Proposed actions

  • Target capability: propose the new shippingAddress on the order through orderUpdate when no label has been created
  • Target capability: propose a UPS Delivery Intercept with request type AA (alternate address), showing the charge before approval
  • Target capability: propose a USPS Package Intercept for a tracked domestic package not yet out for delivery
  • Target capability: propose a decline reply with the reason and the shipment's stage, plus a return or reship offer under your policy
  • Target capability: propose a hold on the fulfillment order while the customer confirms the new address

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

What you can build

  • Edit before the label

    When a Kustomer conversation asks for a new address and the Shopify fulfillment order is still OPEN, propose the orderUpdate and a confirmation reply.

    With Kustomer, Shopify

  • Intercept a UPS package in transit

    Check eligibility for the 1Z number, show the intercept charge, and propose the alternate address request with the reply to the Gorgias ticket.

    With UPS, Gorgias

  • Decline with the scan as evidence

    When Shippo shows the package out for delivery, propose the decline reply that quotes the scan and offers a return label once it arrives.

    With Shippo, Zendesk

Requirements

  • A help desk connector: Gorgias, Kustomer, or Zendesk, with write access for the reply
  • A store connector exposing fulfillment order status and order edits, such as Shopify
  • A UPS account with Delivery Intercept enabled, or a USPS Business Customer Gateway account for commercial intercepts
  • A policy for who pays the intercept charge and when a change is refused
Authentication
Signs requests with the help desk, store, and carrier credentials of the connected listings; there is no separate operator account.

Limits

  • UPS Delivery Intercept is a shipper's request made before delivery; a package already delivered cannot be intercepted
  • USPS Package Intercept excludes items out for delivery or delivered, and redirect to a new address is for commercial senders
  • A new address goes through the same validation as any order; a failed check becomes a query, not a change
  • USPS charges its Package Intercept fee only when the intercept succeeds; UPS quotes its charge per request before you approve

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 Ship-To Change ↗

Questions and answers

What does the person approving actually see?
The customer's request, the shipment's current stage from the store and the carrier, the single action that stage allows, and the reply that goes with it. For an intercept, the carrier's charge is shown before approval.
What record does an intercept leave?
The ticket keeps the reply sent. The order gets a note with the old and new address, the intercept request type, the carrier's confirmation, the charge, the approver, and the time.
Will it ever change an address or file an intercept by itself?
No. It proposes one of three outcomes and waits. If the customer's new address fails validation, it proposes a query instead of a change. It never edits an order after a label exists.
Ask about Ship-To Change

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