Product group: OXID extension |
Oxid version: CE / PE / EE 4.7.x - 6.x |
PHP version: PHP 5.x - PHP 7.4 |
IonCube Loader (free): IonCube loader needed |
Usecase: Marketplace connector |
Licencing options: Retail version |
Product group: OXID extension |
Oxid version: CE / PE / EE 4.7.x - 6.x |
PHP version: PHP 5.x - PHP 7.4 |
IonCube Loader (free): IonCube loader needed |
Usecase: Marketplace connector |
Licencing options: 30 day trial |
Product group: OXID extension |
Oxid version: CE / PE / EE 4.7.x - 6.x |
PHP version: PHP 5.x - PHP 8 |
IonCube Loader (free): no IonCube required |
Usecase: Marketplace connector |
Licencing options: Retail version (open source) |
Export 100% clean and valuable datafeeds out of OXID eShop by using our interface extension for Google Merchant Center / Google Shopping and Google's product listing ads program.
Google and its product search plattform Google Shopping is offering a professional service for distributors to sell single products or whole stacks of products on the worlds most traffic heavy website. Upload product lists via CSV or XML data in so called datafeeds to your private Google Merchant Center account backend, the data can be generated by our software extension in an either manual or automated way. Google fetches the data, parses it and displays it to you in the google backend. With Google's goal to display hiqh quality content on its pages for the best user experience it is your goal to deliver valuable content and rich data within these datafeeds. Well our extension helps you keeping up with the google feed specification, as we only export data to the datafeed that is 100% usable by Google's endpoint. We provide additional input fields in the OXID eShop backend for optimizing your data in the way Google is expecting it, and in case of product variants we provide an easy to understand inheritance system to save you a lot of time.
Our software extension provides addditional functionality for OXID eShop article and category objects and datasets. We provide many additional fields that are not visible in shop frontend to enrich your data and to accomplish the feed specifications. Our software does not require any programming skills and you can install it without changing code or being a rocket scientist.
Google Shopping provides a fixed category tree structure for importing and displaying productlists, the so called taxonomy structure. The taxonomy is a list of categories that can be downloaded in a linebased data format with unique numeric id's. Our extension provides an upload function that accepts the taxonomy file in different languages so that if data changes, you keep up to date with the official Google taxonomy data.
Data inheritance:
Basically it is not neccessary to add each product to a Goolge taxonomy product category one by one. It is better and much faster if you just map the Google taxonomy to your category data. Only if you want to specify the taxonomy mapping within categories with mixed content like sale for example it is needed to provide these products a direct mapping of a Google taxonomy. The export first looks if a direct taxonomy mapping exists on the article and if this is not the case, it looks if the main category of the product has a taxonomy mapping. We export only complete and error free data to the datafeed. To save you time managing product data we provide an inheritance system that inherits parent product data to variants if no data is specified on the variant itself.
Manage your datafeeds in the extensions comfortable campaigns manager. Every campaign stands for a single datafeed export file that is provided in one specified language and currency case. Think of it as of a category structure for export files. The mapping of products to the export files is handled in and drag and drop popup you like in the standard OXID interface. The advantage of filtering for specific mapping criterias saves much time and makes it possible to manage even mappings within large product lists. There is no limitation for how many products can be assigned to an export campaign. In the mapping popup we display active and inactive products. There is no problem in mapping inactive products to the c ampaign. They will be exported if activated later and ignored while inactive.
Manage as many export campaigns (datafeed files) as you like. There is no limitation in the amount of campaigns nor in the amount of articles that are mapped to a campaign. Even the webinterface export script works with big data as well as the command line interface script, a step by step export with the possibility to control the memory consumtion is also provided.
Filter the assignment popup by category, article number, title or ean code. This makes the assignment even possible with large amounts of product data.
Your selected campaigns can be exported manually out of the eShop administration by clicking an export button, or automatically triggered by a cronjob. We even provide two ways of cronjob exports. A command line script that can only be triggered via php_cli. Or a cronjob script that uses curl to manage the export without php_cli. The exports will be generated and saved at the specified locations and with their specified filenams. If you export a campaign again, the existing older datafeed file gets overwritten with the new one.