Brand Protection and MAP Enforcement Software: How Do You Catch a Seller Who Relists Under a New Name Every Week?

Enforcement without identity is a game you cannot win

Your channel manager finds an unauthorised seller listing your flagship product at 22 percent below your advertised price policy. They send a notice. The listing comes down. Nine days later the same product is live again from a seller with a different display name, a different storefront, the same photographs with the same shadow in the corner, and a shipping origin in the same city. Nobody in your team connects the two, because nothing in your process treats a seller as a persistent entity rather than a name on a page.

Meanwhile your authorised dealers, the ones who invested in stock, training and showroom space, are watching their conversion collapse. They call your sales team, not your legal team, and the conversation is about whether the relationship is worth it. Price erosion online does not only cost margin on the diverted units, it degrades the economics of the channel you built deliberately, and channel partners leave quietly.

The tools most manufacturers run are a price monitoring feed, a spreadsheet of known offenders, a template cease and desist letter, and someone searching marketplaces manually on a Friday. Red Points, MarqVision and Corsearch all do real work here, and their takedown machinery is capable, particularly for counterfeits where an intellectual property notice is a clean instrument. Where the model strains is that they run against a generic view of your brand, while enforcement decisions depend on your own authorised dealer list, your regional price rules, your product hierarchy and the judgement of who you are actually prepared to act against.

Collection at scale is an engineering problem with an honest ceiling

The first instinct is to collect everything continuously. That is neither achievable nor useful. Marketplaces rate limit, structures change, and full sweeps of a large catalogue across several sites produce more data than anyone reads.

What a custom build does: tier collection frequency by value at risk. Top revenue products in contested categories get checked daily or better, the long tail gets a weekly sweep, and new listings get checked as they surface, because that is where fresh offenders appear. Use marketplace APIs wherever available since they are stable and permitted, reserving other methods for what the APIs will not give you and staying within terms you have taken advice on. Build collectors as independent adapters per source with their own health monitoring, so a marketplace changing its markup degrades one adapter instead of silently stopping everything while the team reads a quiet week as compliance.

The one metric that matters and nobody measures is coverage: what proportion of listings for your products you actually saw this week. Without it, a report showing 40 violations is meaningless, because you cannot tell whether that is the picture or a corner of it.

Finding your product inside someone else's listing

This is the inverse of normal catalogue work. You are not organising your own data, you are identifying your product inside listings written by people who often do not want you to find them. Titles are deliberately misspelt, model numbers are omitted or altered, your product is buried inside a bundle, listings use lifestyle photographs rather than product shots, and the same item appears under three regional model designations.

What a custom build does: match on a stack of signals rather than a single one. Identifiers where present, model number patterns including the common deliberate corruptions, image similarity against your own official asset library which catches sellers using your product photography, and text similarity against your own descriptions which catches copied bullet points. Then hold a confidence score and route the uncertain band to human review, with those decisions feeding back so the matcher improves against your specific catalogue. A generic matcher cannot learn that your model numbering scheme distinguishes a European variant by a suffix, and that distinction determines which regional price rule applies.

Bundles deserve their own treatment because they are the most common evasion: a seller pairing your product with a cheap accessory can argue the price is not comparable. Say explicitly in the policy how bundles are treated, and detect them rather than letting them fall out of the report.

Seller identity resolution is where the actual value sits

Everything above produces violations. Only identity turns them into enforcement. A seller who relists under a new alias within days is not three offenders, and treating them as three means you send three first warnings and never escalate.

What a custom build does: cluster storefronts into entities using the signals that are hard to change. Shipping origin and handling times. Photograph reuse, detected by perceptual hashing across storefronts, which is remarkably effective because sellers rarely re-shoot. Description text fingerprints. Return address where visible. Business names disclosed on the storefront, which in the United States have become more visible for high volume sellers under the INFORM Consumers Act disclosure requirements. Pricing behaviour patterns, since repricing tools leave a recognisable signature. Then hold the cluster as an entity with a confidence level, an alias history and a full enforcement timeline, so the fourth notice you send is addressed to someone you can prove you have warned three times before.

That escalation history is what makes legal action viable. A single takedown notice is administrative. A documented pattern of one entity relisting after repeated notices is a case.

The policy engine, and the legal ground it stands on

MAP is not one price. It is a price per product, per region, per period, with promotional windows where the floor moves, exceptions for authorised clearance of discontinued lines, and different treatment for advertised price versus checkout price versus price in cart. Encoding that in a monitoring tool built for generic price tracking is where most programmes break down, and the symptom is a violation report full of false positives that the channel team stops reading.

There is also a legal shape you must respect. In the United States, advertised price policies are generally structured as unilateral policies that the brand announces and enforces by choosing whom to deal with, rather than as agreements on resale price, for antitrust reasons, and state law varies in how it treats resale price maintenance. Non-US jurisdictions differ again. Take the structure of your policy from antitrust counsel, and then build software that supports exactly that structure. A practical consequence worth noting: the system should record enforcement as a unilateral decision with the policy version in force at the time, and it should not host negotiation of prices with resellers, because your software's records will one day be evidence about how your policy operated.

What a custom build does: policy as versioned data, with effective dates, product scope, regional scope and explicit bundle and promotion handling. Every violation record cites the exact policy version and clause it breached. False positives fall sharply, and the channel team starts trusting the report again, which is the entire point.

Enforcement cases, test buys and finding the leak

Detection tells you a price is wrong. It does not tell you where the product came from, and that is the question your commercial leadership actually wants answered, because unauthorised sellers rarely manufacture anything. They buy from someone in your authorised network.

The tool for that is the test buy, and it is underused because it is administratively painful. Purchase the item, record the seller, receive it, and read the serial or lot code on the unit. That code maps back through your own shipment records to the distributor or dealer it was sold to. Now you know which authorised partner is diverting, which is a commercial conversation with real weight behind it, and it stops the supply rather than removing one listing.

What a custom build does: test buys as a tracked workflow with budget control, chain of custody on the received item, photographs, and the serial-to-shipment lookup automated against your own distribution records. Then a diversion report by authorised partner, which is the single most valuable output of the whole system. Alongside it, enforcement cases hold every notice sent, the response, the platform ticket reference, the outcome and the reappearance, so escalation to counsel arrives as a complete evidence pack rather than a folder of screenshots.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this is the honest shape. A first release covering collection from your two or three most important marketplaces, listing matching with a review queue, seller identity clustering and a violation queue with notice generation runs $60,000 to $130,000 and ships in 10 to 16 weeks. A full platform adding the versioned policy engine with regional rules, enforcement case management with evidence packs, test buy workflow with serial traceback, diversion reporting by authorised partner and channel health dashboards runs $150,000 to $380,000 phased over 6 to 12 months.

What drives cost up here: the number of marketplaces and regions, since each adapter is separate work with its own maintenance burden. Catalogue size and variant complexity, because 40 SKUs and 4,000 are different matching problems. Image similarity at scale, which adds real infrastructure. Language coverage, if you monitor markets where listings are not in your language. And integration into distribution records for serial traceback, which depends on whether your shipment data carries serial ranges.

What keeps cost down: two marketplaces, one region, your top 50 SKUs by revenue, and manual notice sending in release one. Detection and identity are the hard parts. Sending an email is not.

When Red Points or MarqVision is the right answer

Buy if your problem is counterfeits rather than authorised-channel diversion, if you monitor one or two marketplaces, or if you have fewer than about 50 unauthorised sellers. Counterfeit removal through platform intellectual property programmes is a well-solved service problem and the specialists have both the volume relationships and the takedown workflows. Corsearch is credible where trademark work is the core need. Amazon's own brand programmes are also worth using regardless of what else you run.

Build when two or more of these are true. Your main problem is diversion by your own authorised partners rather than counterfeiting, which no external monitor can diagnose because they cannot see your shipment records. Your MAP policy has regional and promotional structure that generic monitoring keeps flagging incorrectly. Sellers relist under new aliases faster than your process connects them. Your authorised dealers are raising channel conflict as a commercial issue. Or you want the enforcement record to be your own asset, because it becomes evidence and it should not sit with a vendor you might change.

How to choose a developer for brand protection software

Ask how they will measure coverage. A team that only reports violations found is giving you a number with no denominator. Coverage of listings seen against listings believed to exist is the metric that tells you whether the programme is working.

Ask how seller identity clustering works and what happens to a wrong merge. Clustering two genuinely different sellers into one entity leads to an escalation letter that a legitimate reseller can rebut, so the design needs a confidence level, a visible alias history and an easy split.

Ask what they know about collection under marketplace terms. A developer who has done this will raise API-first collection, rate limits and permitted use before you do, and will tell you what they will not do.

Ask whether they can connect a serial number on a test buy back to your own shipment records. That capability is the difference between removing listings forever and stopping the source, and a team that has not thought about it is offering you monitoring rather than protection.

Ask who owns the code, the seller entity graph and the enforcement history, and settle it before kickoff. That entity graph compounds in value every month and it is what makes your fourth notice a case rather than another letter. At Digital Heroes the client owns the repository from the first commit.