# Amazon Direct Fulfillment: From Order to Shipment

Canonical page: https://www.kuudo.com/guides/amazon-direct-fulfillment/

Amazon Direct Fulfillment sends a vendor order straight to the customer. Follow the order, inventory, shipment and exception checks that keep it moving.

Author: Kuudo

## Summary

- Amazon Direct Fulfillment is a 1P vendor program: the customer buys from Amazon, and the vendor ships the order directly to that customer.
- Check program and API access, retrieve the order, decide whether the whole order can ship, acknowledge it, keep each warehouse inventory feed current, and confirm the shipment.
- Amazon pages disagree on some acknowledgement, inventory and confirmation timings. Use the current policy for your vendor account, and keep transaction status and shipment evidence with the order.


Amazon Direct Fulfillment is a Vendor Central program: Amazon takes the customer order and the vendor ships it from its warehouse. Enrollment is a separate account step; the API runs an enabled workflow. For each order, retrieve and accept or reject the whole order, update warehouse inventory, then confirm shipment and verify Amazon processed it. Use the account’s current deadlines.

The operator question is practical: *“Amazon sent us the order. What must happen before the parcel leaves, and how do we know Amazon accepted each message?”* An order visible in a feed is only the beginning. A sent acknowledgement or shipment confirmation can still fail processing.

One unavailable line forces a decision on the whole order. A shipment message that Amazon has not processed leaves a second, quieter gap: the parcel can be gone while the order still looks unfinished. With authorized [Vendor Central MCP](/features/amazon-vendor-central-mcp/) access, the agent checks the actual lines and transaction results. [Amazon Agent Atlas](/features/agent-atlas/) supplies the whole-order and confirmation rules; your warehouse cutoff decides when the exception reaches a person.

## Direct Fulfillment starts with an enabled vendor account, not an API enrollment call

Direct Fulfillment is a first-party vendor flow: Amazon takes the customer order and the vendor ships it from its own facility on Amazon’s behalf. It is distinct from [Fulfillment by Amazon](/guides/vendor-central-vs-seller-central/), where Amazon holds seller inventory in its network. Amazon’s vendor API directory lists orders, inventory, shipping, payments and transaction-status APIs for vendors already in the program. Those operations do not enroll a vendor.

Before an agent reads orders through the Vendor Central MCP, confirm the vendor code and warehouse are enabled for Direct Fulfillment in Vendor Central. Then verify that the connection has the operations and roles this workflow needs. Amazon's workflow guide, listed under Sources, marks `getOrders` as restricted and requiring a Restricted Data Token.

Labels and packing slips can have separate restricted access requirements too; one authorized operation does not prove access to every step. The [EDI or API setup guide](/guides/amazon-vendor-central-edi/) covers the connection routes and their testing.

> **Check access before interpreting an empty feed**
> For a live account, record the enabled vendor code, warehouse, transport route and current policy version before accepting any order. If one is unknown, treat an empty order feed as an access or setup exception rather than proof there are no orders.

## Each Direct Fulfillment order needs a whole-order acknowledgement

Amazon’s Vendor Direct Fulfillment Orders API retrieves new purchase orders with `getOrders` and the details of one order with `getOrder`. The order’s lines, quantities, ship window and warehouse are the starting evidence. The vendor-specific Orders API documentation is listed under Sources below; the seller Orders API is a different surface.

Check every line against physical availability before sending `submitAcknowledgement`. Amazon’s Direct Fulfillment workflow treats an order as a unit: if one line cannot be fulfilled, the whole order has to be rejected. Record the reason and route the case to the operator; do not quietly accept the available lines and assume a partial order can ship. The [Vendor Central MCP](/features/amazon-vendor-central-mcp/) gives the agent the order and acknowledgement tools, subject to the workspace policy for writes.

> **Confirm the acknowledgement clock for this account**
> Amazon’s API tutorial says to acknowledge within 24 hours. Its Direct Fulfillment Electronic Communications Policy gives API, EDI and XML vendors two hours; an order not rejected in that window counts as accepted. The web interface has a one-business-day rule. Use the current account policy and the route actually in use; do not turn the tutorial’s 24 hours into a safe operating deadline.

Keep the original order, decision time, acknowledgement payload, transaction ID and final status together. An API submission is asynchronous. `getTransactionStatus` tells the agent whether Amazon processed it; a successful request alone is not an accepted order state. If the whole order is rejected, update the inventory that made it unfulfillable before another customer order arrives.

## Warehouse inventory and package documents must reflect the accepted order

Direct Fulfillment availability is warehouse-specific. Amazon’s Inventory API guide, listed under Sources below, distinguishes partial updates for changed items from a full warehouse update. In a full update, items omitted from that warehouse feed become unavailable; an accidental omission can zero stock. The agent should name the warehouse and update type in its evidence record before sending `submitInventoryUpdate`, then check the transaction result.

Amazon’s inventory guidance does not state one universal cadence. One page says to update at least daily; another calls for three updates a day. Set the schedule from the current agreement and account policy. For an accepted order, compare the warehouse’s available quantity with the ordered quantity and any pending allocations. If stock is short, route the exception before preparing a parcel rather than substituting a different item.

The [Vendor Central MCP](/features/amazon-vendor-central-mcp/) also exposes Direct Fulfillment shipping operations for labels and packing slips, subject to authorization. Check the order number, line identifiers, item counts and required documents against the order before the warehouse hands off the package. Customer data in a packing slip or label may require restricted access and a Restricted Data Token; do not assume the managed connection holds that role for every account.

## Shipment confirmation needs a processed result and the account’s deadline

After the parcel leaves, `submitShipmentConfirmations` sends the purchase order number, shipped items, ship date, expected delivery date and tracking information to Amazon. Amazon’s shipment-confirmation tutorial, listed under Sources below, requires every purchase-order line to appear; partial fulfillment is not allowed. A floor denial is a separate exception path when the order cannot be shipped.

> **Check the shipment-confirmation clock**
> The published timing instructions differ. Amazon's [Direct Fulfillment operations compliance policy](https://vendorcentral.amazon.com/hz/vendor/members/support/help/node/GR8326D4M2KM6F97) says to confirm within 30 minutes of the carrier leaving the warehouse, after tender. Its API tutorial, listed under Sources, says within four hours after shipment. Use the current account policy, and configure the workflow to meet the stricter applicable clock until the account owner has resolved the difference. Record the physical handoff time and submission time rather than checking only the date.

The Vendor Central MCP can then check `getTransactionStatus`, or the operator can use Vendor Central’s Direct Fulfillment Orders view. Amazon says status can take up to ten minutes to appear after submission. Keep the order open until processing succeeds; on failure, retain the returned reason and escalate it with the tracking record.

A missed Required Ship Date does not itself create the Direct Fulfillment chargeback described in [Amazon’s program policy](https://vendorcentral.amazon.com/hz/vendor/members/support/help/node/GRKUHWZSZ9P2HQJX), though late fulfillment can still hurt customer service and operational standing. Other violations remain separate, so do not copy a Retail purchase-order chargeback rule into this flow.

## What happens next: run one order-to-shipment decision check

Use the following checklist for one purchase order. It is a proposed operating artifact, not a record of an executed customer order. Keep the actual source values and policy version beside each result; the agent can fill it from authorized [Vendor Central MCP](/features/amazon-vendor-central-mcp/) reads and prepare writes for the applicable approval review.

| Check | Evidence to keep | Continue when | Otherwise |
| --- | --- | --- | --- |
| Program and access | Vendor code, warehouse, Direct Fulfillment enablement, authorized operations | The order can be read in the correct account | Resolve enrollment or access before treating the feed as empty |
| Order receipt | Purchase order ID, lines, quantities, required ship date and route | Every line and warehouse is identified | Re-read the order or route an incomplete record |
| Whole-order decision | Physical stock, line check, acknowledgement time and transaction status | The entire order is accepted and the status succeeds | Reject or escalate the whole order under the account policy |
| Inventory | Warehouse, full or partial update, submitted quantities and status | Availability reflects the accepted commitment | Correct the feed; check omitted items on a full update |
| Package handoff | Required labels or packing slip, item count, carrier and handoff time | Package matches the accepted order | Stop handoff and resolve the mismatch |
| Shipment confirmation | Confirmation payload, tracking, transaction ID and final status | Amazon processed it inside the applicable clock | Investigate failure or late submission and retain the exception |

Give the operator a dated decision plan: **ready to ship**, **needs a whole-order decision**, or **needs a failed submission repaired**. The result is useful only when it names the order, warehouse, next owner and policy deadline. A recurring team [Skill](/features/skills/) can preserve those checks, while the operator decides how exceptions and consequential writes are approved.

> **Check other channels when stock is unavailable**
> If unavailable stock caused a rejection, check the same item through the [Selling Partner MCP](/features/amazon-selling-partner-mcp/) where the business also sells it, and through the [Amazon Ads MCP](/features/amazon-ads-mcp/) where it is advertised. In Private Cloud, the [Amazon Agent Data layer and Agent Flow](/features/amazon-agent-flow/) can retain the exception for follow-up. These checks require the corresponding account connections and do not change the Direct Fulfillment acknowledgement rule.

The pattern is simple: source order, physical stock and processed Amazon status must agree before a Direct Fulfillment order is called complete.

*For the connection route behind these steps, read [Amazon Vendor Central EDI: Set It Up or Use the API](/guides/amazon-vendor-central-edi/).*


## Frequently asked questions

### Is Amazon Direct Fulfillment the same as FBA?

No. In Direct Fulfillment, a Vendor Central supplier ships an Amazon customer order from its own facility on Amazon’s behalf. FBA uses inventory stored in Amazon’s fulfillment network for seller orders.

### Can the Vendor Central API enroll my account in Direct Fulfillment?

The published API operations manage an existing Direct Fulfillment relationship; they do not establish program enrollment. Confirm eligibility and enablement with your Vendor Central account team before connecting an order workflow.

### Does missing a Required Ship Date automatically create a Direct Fulfillment chargeback?

Amazon’s Direct Fulfillment program policy says the Required Ship Date violation does not itself carry a chargeback, but missed dates can still affect customer experience and operational standing. Do not apply a Retail procurement chargeback rule to this order; check the current policy and any separate violation on the account.


## Sources

- [Amazon: Vendor Direct Fulfillment Orders API](https://developer-docs.amazon.com/sp-api/docs/vendor-direct-fulfillment-orders-api-2021-12-28-model)

- [Amazon: Vendor Direct Fulfillment workflow guide](https://developer-docs.amazon.com/sp-api/docs/vendor-df-workflow-guide)

- [Amazon: Vendor Direct Fulfillment Inventory API](https://developer-docs.amazon.com/sp-api/docs/vendor-direct-fulfillment-inventory-api-use-case-guide)

- [Amazon: Submit shipment confirmations](https://developer-docs.amazon.com/sp-api/docs/submit-shipment-confirmations)

- [Amazon: Get transaction status](https://developer-docs.amazon.com/sp-api/docs/get-the-transaction-status)

- [Amazon: Direct Fulfillment Electronic Communications Policy (Vendor Central sign-in)](https://vendorcentral.amazon.com/hz/vendor/members/support/help/node/GAB9M3VTPLFDJ8PK)

- [Amazon: Direct Fulfillment operations compliance (Vendor Central sign-in)](https://vendorcentral.amazon.com/hz/vendor/members/support/help/node/GR8326D4M2KM6F97)

- [Amazon: Direct Fulfillment program policies (Vendor Central sign-in)](https://vendorcentral.amazon.com/hz/vendor/members/support/help/node/GRKUHWZSZ9P2HQJX)