Skip to main content

FBPI Terminology

A collection of commonly used terms in the FBPI (Fulfilled by Partner Integration) ecosystem.
Use this glossary to quickly understand key concepts referenced throughout the documentation.

Acknowledgment​

The response your system sends back to noon after receiving an order notification. An acknowledgment confirms whether the item can be fulfilled.

API Key​

A credential used to authenticate and authorize API or webhook requests between your system and noon.

Delivery Model​

A configuration that defines how shipments move through noon’s logistics network (e.g., domestic, bulky, or cross-border).

Drop-off​

A handover method where the seller delivers the prepared shipments to a noon facility.

FBPI (Fulfilled by Partner Integration)​

noon’s fulfillment model where sellers operate their own warehouses and integrate directly with noon’s systems through APIs.

Handover Type​

Indicates how shipments reach noon: either pickup by noon’s courier or drop-off by the seller.

Integration Warehouse​

A warehouse code created specifically for the FBPI fulfillment model. It is required for receiving orders and syncing stock, price, and shipments via API.

Killed Order​

An order that failed webhook delivery after multiple retry attempts. These orders require investigation through the Orders Dashboard.

Manifest / Manifestation​

The step where sellers create a list of shipments that are ready for handover. In FBPI, this is done manually through Seller Lab.

Order Notification​

An event sent from noon to the seller’s webhook containing order details that require acknowledgment and further processing.

Pending Order​

An order that has been sent to the webhook but has not yet been acknowledged by the integrator or system.

Pickup​

A handover method where noon’s courier collects shipments directly from the seller’s warehouse.

Processing Time​

The time a seller needs to prepare a shipment before noon can collect it.

Return to Origin (RTO)​

The process through which returned or undelivered items are sent back to the seller's warehouse.

Service Account​

A special type of account used by systems—not humans—to authenticate and interact with noon’s APIs.
Service accounts hold API credentials and permissions that allow automated integrations to function securely.

Shipment Creation​

The API step where the integrator or system generates a shipment for an acknowledged order and submits it to noon for label generation.

Stock Sync​

The automated process of sending inventory quantities from the seller’s system to noon using the Stock API.

Webhook​

A publicly accessible endpoint provided by the integrator or seller's system.
noon uses this endpoint to push real-time order notifications.
Your system must receive, process, and respond to these events promptly to avoid Pending or Killed orders.

Warehouse Activation​

The final step in warehouse configuration where the warehouse is switched to "Active," allowing it to start receiving orders via FBPI.