> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/technical-guides/channel-app-template/architecture/services-flows/product-service.md). # Product Service The Product Service handles the actions of creating, updating, and deleting products. To perform these actions, it relies on integrations with OmnitronIntegration and ChannelIntegration. ### *class* ProductService *(object)* #### Insert Products *(self, add\_mapped=True, add\_stock=True, add\_price=True, add\_categories=True, is\_sync=True, is\_success\_log=True)* This function first connects to Akinon Omnitron and retrieves the products that can be added to the sales channel. Based on the provided parameters, it fetches product mapping information for `add_mapped`, stock information for `add_stock`, price information for `add_price`, and category information for `add_categories` from Akinon to send to the sales channel. Subsequently, these details are transmitted to the Sales Channel via the `send_inserted_products` command. The value of the `is_sync` parameter determines whether the communication with the sales channel will be synchronous or asynchronous. If it is asynchronous, the necessary records are created through `batch_service`. If an error occurs, an `error_report` is generated in the Sales Channel Logs. #### Update Products *(self, add\_mapped=True, add\_stock=True, add\_price=True, add\_categories=True, is\_sync=True, is\_success\_log=True)* This function first connects to Akinon Omnitron and retrieves the products that can be updated in the sales channel. Based on the provided parameters, it fetches product mapping information for `add_mapped`, stock information for `add_stock`, price information for `add_price`, and category information for `add_categories` from Akinon to send to the sales channel. Subsequently, these details are transmitted to the Sales Channel via the `send_updated_products` command. The value of the `is_sync` parameter determines whether the communication with the sales channel will be synchronous or asynchronous. If it is asynchronous, the necessary records are created through `batch_service`. If an error occurs, an `error_report` is generated in the Sales Channel Logs. #### Delete Products *(self, is\_sync=True, is\_content\_object=True, is\_success\_log=True)* This function first connects to Akinon Omnitron and retrieves the products that can be removed from the sales channel. Subsequently, these details are transmitted to the Sales Channel via the `send_deleted_products` command. The value of the `is_sync` parameter determines whether the communication with the sales channel will be synchronous or asynchronous. If it is asynchronous, the necessary records are created through `batch_service`. If an error occurs, an `error_report` is generated in the Sales Channel Logs. #### Get Delete Product Batch Requests *(self, is\_success\_log=True)* This function first connects to Akinon Omnitron and retrieves the `batch_requests` that have been sent to delete products from the sales channel and are still processing. It then queries the Sales Channel using the `check_deleted_products` command. If an error occurs, an `error_report` is generated in the Sales Channel Logs. Finally, it completes the flow by sending the response received from the sales channel back to Akinon Omnitron. #### Get Product Batch Requests *(self, is\_success\_log=True)* This function first connects to Akinon Omnitron and retrieves the `batch_requests` that have been sent to create or update products in the sales channel and are still processing. It then queries the Sales Channel using the `check_products` command. If an error occurs, an `error_report` is generated in the Sales Channel Logs. Finally, it completes the flow by sending the response received from the sales channel back to Akinon Omnitron. --- # 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.akinon.com/technical-guides/channel-app-template/architecture/services-flows/product-service.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.