外掛標籤
開發者團隊
原文外掛簡介
Create and update XML and CSV feeds for Idealo from WooCommerce.
Generate XML and CSV feeds with automatic updates every 15 minutes.
Sync offers with Idealo in real time via the PWS API.
PRT Feed for idealo connects WooCommerce to PRT’s external catalog service. PRT servers retrieve native product data over authenticated HTTPS, evaluate the catalog, generate XML/CSV and host the current feeds. The PRT scheduler rebuilds every 15 minutes and after detected product changes, independently of visits or WordPress cron. Your HTTPS store must remain reachable with this connector active.
All local functionality included in this directory plugin is available without a license check. It includes connection settings, native catalog export, authenticated transport, a mirror of the hosted results, an anonymous aggregate access counter, and the PWS transport. The external feed service requires a PRT subscription because generation, publication and hosting take place on PRT servers. This is not a license-only service.
Advanced local configuration, the assistant interface, statistics dashboards and email report generation are not included here. They are supplied in the separate PRT idealo Premium component, manually downloaded and installed by the store administrator outside WordPress.org. This plugin does not install, download or update that component. It uses the same existing PRT subscription, not a second subscription.
The interface supports Italian, English, German, French and Spanish. PRT provides an independent integration. No endorsement by idealo or WooCommerce is implied.
Paid PRT service
The existing subscription is EUR 9 per month including VAT, with automatic renewals until cancelled and one 21-day trial per eligible store. Initial approved checkout includes the configuration/statistics option, 300 authorized clicks per paid cycle and EUR 0.03 per additional authorized click. Trial clicks are not billed. Installing either component alone never authorizes payment or changes an existing option. Stripe checkout requires the manager’s explicit acceptance.
The premium component supplies advanced local features and their access controls. Disabling its option retains the same EUR 9 base subscription, continues feed and PWS with base rules, and preserves customizations for later restoration. New events during the disabled interval are not retroactively charged. Anonymous aggregate counts are distinct from consented attribution and billing events.
Deactivating only the premium component first reconciles outstanding authorized usage and disables its option, leaving the base subscription and connector active. Deactivating or uninstalling the connector cancels the PRT subscription after successful reconciliation. If PRT is unreachable, the operation stops with an error instead of claiming cancellation succeeded.
Product information: https://www.prtflow.com/idealo-woocommerce
Service terms: https://prtdev.com/apps/idealo-woocommerce/legal.php?document=terms&lang=en
Privacy: https://prtdev.com/apps/idealo-woocommerce/legal.php?document=privacy&lang=en
Support: https://prtdev.com/apps/idealo-woocommerce/legal.php?document=contacts&lang=en
Requirements
WordPress 6.7 or later, WooCommerce 9.5 or later and PHP 8.2 or later.
PHP sodium, mbstring, DOM and XMLWriter. WooCommerce Action Scheduler.
A reachable HTTPS store and an active PRT subscription for hosted feed generation.
Your own idealo account and verified credentials for optional PWS.
HPOS compatible. Third-party pricing, tax, shipping, multilingual and currency extensions require verification with the actual catalog. Currencies are not automatically converted. Review product eligibility and industry-specific required attributes before publishing.
External services and data
PRT
Endpoint: https://prtdev.com/apps/idealo-woocommerce/api.php
A fresh installation does not contact PRT until the administrator accepts the service summary and presses Proceed. Registration transmits the installation ID, HTTPS store URL, authentication token, private feed-token hash, connector version and return URL. After registration, authenticated scheduled requests synchronize native product titles, identifiers, prices, stock, images, product links and export conditions. The service evaluates and groups offers, hosts the XML/CSV output and returns a signed data-only mirror. Feed links contain access tokens, so share them only with authorized recipients.
PRT receives subscription choices, explicit authorizations and previously authorized usage event IDs/times during reconciliation. The connector can reconcile outstanding events created by the separate component even if that component is no longer active. It does not send raw orders, customer names, addresses, visitor IP addresses or PWS credentials to PRT. No visitor identifier or unique browsing history is created by its aggregate counter.
Terms: https://prtdev.com/apps/idealo-woocommerce/legal.php?document=terms&lang=en
Privacy: https://prtdev.com/apps/idealo-woocommerce/legal.php?document=privacy&lang=en
Stripe
Payment and subscription management use https://checkout.stripe.com and https://billing.stripe.com . The PRT server communicates with Stripe. This plugin does not receive card details or a Stripe secret key.
Terms: https://stripe.com/legal
Privacy: https://stripe.com/privacy
idealo PWS
idealo internet GmbH provides the optional Partner Web Service (PWS) to keep the merchant’s offers synchronized with idealo. No request is sent to idealo until the administrator enters their own credentials and explicitly verifies the connection. Verification sends the client ID and secret over HTTPS to https://api.idealo.com/mer/businessaccount/api/v1/oauth/token to obtain an access token. Credentials remain encrypted in WordPress and are not sent to PRT.
Only after the administrator also enables PWS, local scheduled synchronization sends the authorized bearer token, idealo shop ID, offer SKU and current offer fields to https://import.idealo.com/shop/{shop}/offer/{sku}. These fields can include product titles, identifiers, descriptions, prices, availability, delivery/payment/shipping conditions, images, product URLs and product-specific attributes. The adapter creates or updates offers, reads them back for verification and removes offers that are no longer eligible. It does not send orders or customer information to idealo. Bulk removals require a separate confirmation. Disable PWS to stop scheduled synchronization.
This local adapter is not license-gated. It operates on a fresh authenticated service mirror and stops when that data is unavailable or stale. API acceptance is not proof of final publication on idealo. The merchant’s actual listing agreement and country-specific conditions remain applicable.
Terms of service for merchant listings: https://partner.idealo.com/partner-idealo-com/uk/gtc
Privacy policy for business customers: https://partner.idealo.com/partner-idealo-com/de/datenschutzerklaerung
Merchant account and applicable agreements: https://business.idealo.com/
API documentation: https://idealo.github.io/idealo-partner-api-docs/
Feed documentation: https://idealo.github.io/csv-importer/en/csv/
Privacy
The local counter records hourly product access totals from valid signed idealo landing links. It does not store visitor cookies, sessions, IP addresses, user agents or unique visitor records. Staff, recognizable bots and prefetches are excluded. It is an aggregate count, not a guaranteed unique human-click measurement. Ordinary hosting logs are separate.
The separate premium component documents its own optional consented attribution, assistant and reports. Those implementations are not included in this directory package. Customer and order data remain in WooCommerce. Review the service privacy notice and your own obligations before enabling data sharing.
Source code and packaging
All PHP, JavaScript and CSS source files are included in this plugin. The files in assets/ are the human-readable, directly maintained runtime sources, not compiled or minified bundles. There are no third-party JavaScript libraries in this connector. No npm, webpack, transpilation, minification or external source download is needed to modify or run it.
assets/admin.js handles only the language form’s native POST submission. assets/clean-link.js removes the signed product landing parameters from the visible browser address after the server has processed the request. CSS files contain the shared PRT interface styles and the WordPress host adapter.
No build step is required to use or modify the readable PHP, JavaScript and CSS files. Development-only Python tools are excluded from the installed plugin.
The standalone packaging script is publicly available at https://prtdev.com/apps/idealo-woocommerce/source/prt-feed-for-idealo-2.1.4-build.py.txt . Save it as build-package.py outside the plugin directory, then run:
python3 build-package.py /path/to/prt-feed-for-idealo /path/to/prt-feed-for-idealo-2.1.4.zip
This uses only the Python 3 standard library and creates a ZIP with one prt-feed-for-idealo/ root. Packaging copies these same readable runtime sources without compiling, obfuscating or transforming them. The script excludes development tools, hidden files, caches and unsupported file types. A JavaScript formatter may be used while editing. It is not a build dependency and no generated counterpart is required.
Request security
Administrative changes use POST forms with wp_nonce_field(‘prt_idealo’). The handler rejects other HTTP methods, checks current_user_can(‘manage_woocommerce’) and validates check_admin_referer(‘prt_idealo’) before processing input. Payment actions also require their own explicit confirmation. Visiting an admin screen or reading a return selector does not authorize checkout, cancellation, consent or configuration changes.
The server-to-server connector is not a browser-admin action. It requires a bounded POST JSON body, an installation-bound HMAC, an exact installation identity and a five-minute timestamp window. A WordPress session nonce is not an authentication mechanism for an external scheduler. The ownership challenge is read-only and returns only a keyed proof. Feed redirects require the private feed token. Public product counts require the exact product HMAC and the eligibility checks documented above. None of these machine/public routes relies on a privileged browser cookie.
