> For the complete documentation index, see [llms.txt](https://docs.shippify.co/developers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shippify.co/developers/en/integration-guide/basic-processes/delivery-creation.md). # Delivery creation This process is fundamental in the integration because you will need to import orders from your external platform to Shippify. Once the deliveries are in our system, they can be manipulated within it, whether to edit them, create routes, change states, or other functionalities that Shippify has. There are several ways to achieve this process, and we will classify them based on the volume of deliveries you make to give you a guide on which one to use.

**For low volume**: Less than 10 deliveries per day.

**For medium-low volume:** Between 10 and 100 deliveries per day.

**For medium-high volume**: Between 100 and 500 deliveries per day.

**For high volume:** More than 500 deliveries per day.


	Dash	Manual and individual creation of orders through the platform.
	Import	Batch manual creation of orders through the platform by importing a file.
	Zapier	Order creation through an action in Zapier.
	API	Order creation in batches or individually by consuming our API.
	SFTP	Batch order creation by uploading a file to an SFTP.
	Customized	Order creation by a process requested by the client.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.shippify.co/developers/en/integration-guide/basic-processes/delivery-creation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.