Meta data allow adding structured information to products, categories, or orders that the eshop system or API does not natively support. They are key for synchronizing special data between Fynode and your eshop, optimizing for AI, SEO, or expansion into multiple countries.
- They are custom fields or extended attributes that enable storing additional information outside the basic model of products, categories, or orders.
- Fynode uses meta data to synchronize data such as: product SEO title, SEO description, extra descriptions, shipment numbers, document links (PDF, tracking), specific identifiers, or custom fields unique to the client.
¶ Main functions of meta data
- Extended enrichment of products/categories/orders: Inserting data outside the platform's basic model.
- Synchronization of specialized data: Example – pickup point, shipment number, invoice link, special notes.
- Support for AI generation and translations: Where there is no native field for SEO texts, generated data is stored in meta data.
- Multilingual support: Storing texts and key information for each localization separately.
- Targeted exports/imports to external systems.
- SEO title of the product (meta:
seo_title)
- SEO description of the product (meta:
seo_description)
- Short or long descriptions if not available natively – optionally stored in meta data with a custom field name
- Additional identifier or extended properties (e.g., “warranty_years”)
- Stock info for multistore / multi-warehouse
- SEO title of the category (meta:
seo_title)
- SEO description of the category (meta:
seo_description)
- Short and long descriptions if not available directly via API
- Possible creation of an internal key for specific category labeling
- Shipment number (meta: e.g.,
tracking_number)
- Links to PDF invoices (
pdf_regular, pdf_proforma, pdf_cancel)
- Public link to the order (
public_url)
- Pickup point ID (e.g.,
pickup_point_id)
- Custom fields for customer or export (e.g., “custom_note”)
- In the Eshop Settings, you can specify the names of meta data supported by the platform for each connected eshop.
- For example, if the pickup point ID in API is
pickup_point_id, enter this name in the relevant field. The system then maps the Fynode field to the API meta field of the platform.
- Changes to meta data settings apply only to newly uploaded or synchronized data; existing items will be overwritten only after synchronization.
- If a field originates from meta data, it will be displayed with a label, e.g., “SEO title (meta: seo_title)”.
- Editable meta data can be modified at any time and for each language separately (if the eshop supports multiple localizations).
- When AI generation is used (e.g., SEO texts), AI outputs are automatically stored in the correct meta field according to system settings.
¶ Best tips and recommendations
- Fill in meta fields accurately according to your platform's documentation to ensure proper synchronization.
- For AI generation and translations, it is recommended to generate/save the value in the main localization first, then translate into other languages.
- During migration/unexpected meta data changes, configure export or synchronization at the item level.