Drezzy Integration

Drezzy runs on a cost-per-click (CPC) model rather than a flat listing fee: retailers are charged only when a shopper clicks through to their store, not simply for appearing in the catalog. For fashion, footwear and accessories sellers, that makes it a comparatively low-risk way to add another Italian (and Spanish) demand channel alongside better-known price comparison sites.

Because Drezzy shares its parent company's feed infrastructure with Trovaprezzi and Shoppydoo, several feed-management tools bundle all three destinations together — a feed built for one can often be reused, with light adjustments, for its sister channels.

Drezzy does not pull in a feed URL cold. Retailers first apply through Drezzy's partner/advertiser sign-up process; third-party integration guides describe a review step (one feed-tool vendor cites roughly a 48-hour initial response) before a store is approved to advertise. Once approved, Drezzy issues account credentials — referred to in some feed-generator tools as a merchant key — that must be entered into your feed-generation app before Drezzy will display your catalog.

In practice this means the feed is the second step, not the first: account/budget setup with Drezzy comes before the feed goes live, and the feed's job afterward is to keep the already-approved listing current.

Third-party integration guides and feed generators consistently describe Drezzy accepting structured product feeds in CSV, XML or TXT format, delivered as a file hosted at a stable, automatically refreshed URL rather than a one-off manual upload. This mirrors how Drezzy's sister sites in the 7Pixel network (Trovaprezzi, Shoppydoo) are integrated, and several feed apps — including ones built for Shopify — generate a single combined Trovaprezzi/Drezzy feed from the same underlying export.

We could not locate an independent, official technical feed specification published by Drezzy itself; retailers are generally pointed to a feed-generation tool or their Drezzy account contact for the exact schema to use.

No official, field-by-field Drezzy feed dictionary is publicly available (Drezzy's own partner pages were not reachable during research). Because Drezzy shares feed tooling with Trovaprezzi, the fields that tooling commonly asks sellers to fill in — product name (without promotional slogans), brand, a short plain-text description, price including VAT, a category assigned from the platform's category tree, an EAN or manufacturer product code, and at least one product image — are a reasonable starting baseline, since they're what the shared feed-generation tools request. Treat this as a practical starting point rather than a confirmed Drezzy requirement, and confirm the exact field list with Drezzy or your feed tool once your partner account is approved.

1. In Feedance, create a new product feed and choose CSV or XML as the output format — the formats Drezzy's ecosystem is documented to accept.
2. Apply for a Drezzy partner/merchant account if you haven't already, and wait for approval, since Drezzy needs to authorize your store before it will process a feed.
3. Once approved, map your Feedance product fields to Drezzy's expected structure — at minimum product name, brand, price, category, image and a unique identifier such as an EAN or SKU — adjusting the mapping if Drezzy's account team specifies a different schema.
4. Publish the Feedance feed URL and share it with Drezzy through your partner account or account contact, since submission is typically by feed link rather than manual file upload.
5. Schedule the feed to refresh automatically in Feedance so price, stock and new-product changes reach Drezzy without manual re-submission.

Partner-facing material for Drezzy describes catalogs being sent on a daily basis, with Drezzy then updating prices, availability and new products from that file. The feed-management platforms used to connect to Drezzy generally support more frequent refreshes (hourly or near-real-time) if your catalog changes quickly, but daily is the cadence explicitly associated with the Drezzy/7Pixel relationship in the sources we found, so treat that as a practical minimum for keeping prices and stock accurate.

These are general product-feed best practices rather than instructions confirmed by Drezzy specifically:

1. Keep product titles free of promotional language such as "sale" or "free shipping," leading instead with brand and product type — comparison engines in this category typically penalize slogan-style titles.
2. Fill in brand and an EAN or manufacturer code wherever you have one; comparison and marketplace engines use these identifiers to match and de-duplicate offers across sellers.
3. Map your internal categories to the destination's category tree as specifically as possible rather than leaving items in a generic top-level category.
4. Keep price and stock fields synced with your storefront as close to real time as your platform allows — on a CPC channel, a click that lands on an out-of-stock or mispriced item is spend wasted for no possible sale.

Does Drezzy charge for listing products? No — available material describes a cost-per-click model, so you pay only when a shopper clicks through to your store, not for appearing in the catalog.

Can I reuse the same feed for Trovaprezzi and Drezzy? Often yes, with adjustments. Since both sites are owned by 7Pixel, several third-party feed-generation tools produce a combined Trovaprezzi/Drezzy feed from one export, though field mapping may still need review for each destination.

Do I need approval before submitting a feed? Yes. Integration guides describe a partner sign-up and review step before Drezzy activates a store's listings, so budget time for approval before your feed goes live.

Is Drezzy only for the Italian market? Its primary site targets Italian shoppers; 7Pixel also operates a Spanish counterpart at drezzy.es, so the same feed approach generally extends to that market through a separate account.