> For the complete documentation index, see [llms.txt](https://help.orderdesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orderdesk.com/start-here/print-on-demand-video-series/sending-orders-to-the-printer.md). # Sending Orders to the Printer {% embed url="" %} Previous video ### FAQ **Once I submit the order, how will I know the printer has received it?** Every successful order submission will be recorded in the Order History. You can know that an order has been received by the printer when you see the message “Order Submitted to *Your Printer*.” **I don’t understand the error message indicating why the order didn’t submit. What does it mean?** Different error messages can mean different things, but it’s important to know that some error messages are coming directly from the printer themselves. If the error is not related to the order missing print details, you will usually be best served asking your *printer* what the error message means, as it’s likely the Order Desk support team won’t be able to say for certain. **I needed to make a change to the order after it was submitted. How do I send my printer the update?** Once an order has been submitted, we don’t have a way to make additional updates to it at your printer. As a result, if you need to make changes to a submitted order, you’ll need to reach out to your printer directly to have them make that update on their end. **What do I do if an order contains some items that don’t need to be sent to the printer?** If you only need to send the printer some of the items, you would need to look into either [splitting your orders](/guided-walkthroughs/orders-and-folders/how-to-split-orders.md) (to remove the items the printer won’t be fulfilling), or using [a product code skip](/integration-setup-guides/fulfillment-services/fulfillment-integration-product-settings.md#product-code-skip) to tell us to exclude those items when sending the order to the printer. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.orderdesk.com/start-here/print-on-demand-video-series/sending-orders-to-the-printer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.