> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/product-catalog/product-catalog/products-with-physical-delivery.md). # Products with physical delivery ## Overview 2Checkout is your reliable payment partner for receiving payments from customers worldwide. Depending on your business model, you can opt for selling **electronic** or **physical** products. ## Catalog physical products Use the Control Panel to manage your catalog of physical products, with advanced control over attributes such as **handling fee** and **product weight**. Create shipping methods that will be displayed to your customers in the cart, based on product weight, customer location, and other filters that you control. You can later confirm the shipment of your tangible products to your customers. ## Dynamic physical products 2Checkout enables you to receive orders placed with dynamic product information, even if you are selling tangible products. Read [this](/orders/orders/orders-with-dynamic-product-information.md) article to learn more about orders placed with dynamic product information. --- # 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://docs.2checkout.com/product-catalog/product-catalog/products-with-physical-delivery.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.