Allani Integration

Because Allani doesn't process the sale itself, the product feed is effectively the only way a retailer's catalog reaches its audience: every item a shopper sees, saves into an outfit, or clicks through to buy started as a line in that retailer's feed. For fashion and apparel sellers targeting shoppers in Poland or Brazil, that makes the feed the entire storefront on Allani, not a supplementary listing.

Because the platform is curation- and outfit-led rather than a plain search-and-filter marketplace, complete and accurately categorized data (correct category, size, color, material) matters more here than it would on a bare price-comparison site: Allani's editorial and outfit-matching logic depends on that data to decide where and how a product gets surfaced.

Two mechanics come up consistently and independently across the certified store-platform integrations built for Allani (documented separately by home.pl, SOTE and Sellingo, among others):

1. Every product must be assigned to a main (parent) category in the feed. Products left uncategorized, or attached only to a sub-category with no parent, are documented to be dropped from the feed entirely rather than shown miscategorized -- they simply don't appear on Allani.
2. Allani assigns each connected store an account manager who works with the merchant on which tools and promotional placements to use. Onboarding is relationship-led rather than a fully automated self-signup, which differs from a purely automated comparison engine.

Neither mechanic is specific to any one feed tool -- they're structural to how Allani ingests and manages partner catalogs.

Allani does not publish its own public, merchant-facing feed specification the way a large ad platform typically would. What's documented instead comes from the certified apps that connect major e-commerce platforms (Shoper, Shoplo, SOTE, home.pl-hosted stores, Sellingo) to Allani, and they agree on the basics: Allani ingests a product feed in XML format, generated by the merchant's store or feed tool and made available at a hosted URL that Allani, or the merchant's Allani account manager, is given access to.

Beyond "XML file at a URL," exact tag names, encoding rules, and file-size limits are not publicly documented by Allani itself -- they're implemented per platform inside each certified app. We're keeping this section general rather than inventing tag-level specifics: if you need the literal XML schema for your setup, your Allani account manager is the authoritative source, and Feedance's role is to produce a correctly structured, up-to-date export that matches whatever schema your integration path requires.

No single official Allani document lists a definitive attribute set. The table below reflects fields that recur consistently across multiple independent, certified Allani integration guides (home.pl, SOTE, Shoper) rather than a single Allani-published spec -- treat it as a reliable working list, not a verbatim Allani schema.

Exact field names, and whether a given attribute is mandatory or optional, can vary by which platform or app you connect through, since Allani itself doesn't publish one canonical schema directly to merchants.

Because Allani's onboarding is manager-led rather than fully self-serve, the practical path looks like this:

1. Confirm you have, or apply for, an Allani partner account and account manager -- this is typically arranged directly with Allani, not through a feed tool.
2. In Feedance, create a feed and map your catalog's category, price, image, and fashion attribute fields (size, color, gender, material) into a clean, exportable structure.
3. Make sure every product is mapped to a valid main category -- Feedance flags products missing a parent category so they aren't silently dropped from what Allani receives.
4. Generate the feed as a hosted XML file and share the resulting URL with your Allani account manager, who registers it on Allani's side.
5. Monitor the feed in Feedance for validation issues (missing images, empty prices, uncategorized items) before each refresh reaches Allani.

Allani doesn't publish a fixed refresh interval; the certified integration apps generate the XML file on a cyclic schedule once activated, with the exact cadence controlled by the connecting platform rather than by Allani itself. As a general practice for fashion catalogs -- where size availability and pricing change often -- refreshing at least once a day is a sensible default, with more frequent updates during promotions or fast-selling drops. Feedance can run on that cadence automatically so stock and price data don't drift out of sync between updates.

The one specific, documented failure mode that shows up consistently across Allani's certified integrations is category assignment: a product that isn't attached to a main (parent) category doesn't appear with a warning -- it's simply absent from the feed Allani receives. If products you expect to see on Allani aren't showing up, check category mapping first.

Beyond that documented case, general feed-hygiene issues that affect any fashion feed can also block visibility: missing or broken image URLs, empty price fields, and size or color variants that aren't mapped consistently. These are general best practice rather than Allani-published error messages, since Allani has not published its own error catalog.

The following are general fashion-feed best practices, not Allani-specific requirements:

1. Keep every product under a real parent category -- never leave items only in a sub-category.
2. Fill in size, color, material, gender and pattern wherever you have the data; these drive outfit-matching and filter placement on curation-led platforms like Allani.
3. Use clean, high-resolution primary images -- Allani's presentation is visual and outfit-led, so image quality affects clickthrough more than on a plain price list.
4. Keep stock and price fields current; a stale feed during a sale event misrepresents availability to shoppers who click through.

Is Allani a marketplace or a comparison/discovery site?
Functionally it's a discovery and outfit-curation platform: shoppers browse and save looks on Allani, but checkout happens on the retailer's own site. For feed purposes it behaves like a comparison-engine integration -- XML feed, category-gated visibility.

Which markets does Allani serve?
Allani's primary market is Poland (allani.pl), with a separate presence in Brazil. Combined, Allani reports reaching over 2 million shoppers monthly.

Do I need Allani's approval before sending a feed?
In practice, yes -- onboarding runs through an Allani account manager rather than a fully automated self-signup, so plan for a relationship step alongside the technical integration.

Can Feedance push directly into Allani, or do I still need a store-platform app?
Feedance builds and hosts a correctly structured XML feed for you; how that feed URL gets registered on Allani's side, directly with your account manager or via a certified store-platform app, depends on how your existing Allani partnership was set up.

Why are some of my products missing from Allani even though they're in my feed?
The most commonly documented cause is a missing main/parent category -- Allani's integrations drop uncategorized products rather than showing them miscategorized.