> ## Documentation Index
> Fetch the complete documentation index at: https://egentify.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Fulfillment Integrations for Egentify: ShipStation and Ordoro

> Connect ShipStation or Ordoro so Egentify blocks cancellations on orders that already shipped and stops the warehouse when a cancellation goes through in time.

Egentify's AI support agent cancels orders and changes shipping addresses on your customers' behalf. Whether that is safe to do depends on something your store often does not know yet.

Your store and your warehouse do not always agree. An order can still read "unfulfilled" in Shopify or WooCommerce while ShipStation has already printed the label. Cancel and refund in that window and the box ships anyway.

Connecting a fulfillment platform closes that gap.

> **[ShipStation](https://egentify.com/docs/integrations/shipstation.md)**
>
> Connect with a V1 API key and secret

> **[Ordoro](https://egentify.com/docs/integrations/ordoro.md)**
>
> Connect with a client ID and secret, Premium plan or above

## What the connection does

This is a safety check, not a new agent skill. Your customers never see it and the agent never mentions it. It changes three actions that already exist:

* **Order cancellation from the chat widget**
* **Order cancellation from a ticket**
* **Shipping address changes**, from both chat and tickets

In each case Egentify asks your fulfillment platform whether the order has shipped before touching anything. Cancellations are blocked once an order has shipped. When a cancellation is still allowed, the warehouse is halted **before** the store cancel and refund, so you never refund an order that ships anyway.

Split shipments are handled together: if any package has shipped, the whole order counts as shipped.

> [!NOTE]
>
> Tracking numbers and delivery updates do not come from this integration. The agent reads those from your store. Connecting a fulfillment platform does not change what the agent can tell a customer about where their parcel is.

## Choosing between them

Both close the same gap. They differ in what happens to dropshipped orders.

| | ShipStation | Ordoro |
| - | - | - |
| Blocks cancels after shipping | Yes | Yes |
| Halts the warehouse on cancel | Yes | Yes |
| Cancellation reaches the supplier | No | Yes, if Ordoro has enabled it on your account |
| Supplier email shown to your team | No | Yes |
| Dropshipped orders stay address-editable | No | Yes, before shipping |
| Third-party plan needed | None stated | Premium or above |

## How verification works

Both platforms can hold orders from several storefronts. ShipStation calls these **stores**, Ordoro calls them **carts**. Order `#1001` is ambiguous across a whole account, so Egentify needs to know which channel holds this store's orders.

When you verify, Egentify:

1. Fetches the channels in your account.
2. Tries to match one automatically by comparing its configured URL to your store's address.
3. Takes your five most recent store orders and confirms it can actually find one of them in that channel.

That last step is the real test. A channel that returns "order not found" looks identical to "order not shipped", which is exactly the mistake that would let a shipped order be cancelled and refunded.

If the automatic match is ambiguous, the picker opens so you can choose the right channel yourself.

## Reading the status

| Status | Meaning |
| - | - |
| **Not connected** | No credentials saved yet |
| **Connected, verify to map** | Credentials saved, no channel mapped |
| **Channel not verified** | A channel is mapped but the order check has not passed |
| **Verified** | Working, with the date it was last checked |

> [!WARNING]
>
> An integration that is switched on but not verified **blocks cancellations** rather than being ignored. This is deliberate: if Egentify cannot confirm an order has not shipped, it will not let the order be cancelled. Finish verifying, or switch the integration off.

## What un-verifies a connection

Verification is cleared automatically when you rotate your API credentials, change the mapped channel, or change your store's URL or platform. The Integrations tab shows an amber dot and the status drops to **Channel not verified**. Click **Re-verify** after any of those changes.

## Orders already sent to the warehouse

By default, Egentify declines to cancel or re-address an order that has reached your fulfillment partner but has not shipped, because the partner may not see the change.

Once a fulfillment integration is on, two extra settings appear on the **Agent** tab. Both are off by default:

* **Also change orders already sent to fulfillment**
* **Also cancel orders already sent to fulfillment**

Turning either on lets the action go through where the platform allows it. You are alerted and are expected to confirm with your partner directly. Orders that have already shipped stay blocked either way, for everyone.

## Limits worth knowing

* One account per provider, per store. You cannot connect two ShipStation accounts to the same store.
* Order matching uses your store's order number exactly.
* If Egentify cannot halt an order in your warehouse, it does not cancel in your store either, and flags the order for review. This protects you from refunding an order that then ships.

## Who can set this up

Owners, admins, and Technical Specialists can connect and verify. Chat Supervisors see these settings in read-only form.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.