LabelFlow Violations: Billing Violations and Disputes

See every violation record in one list: how many there are, which merchants are involved, and the type, detail and time of each record — filtered by merchant when you need to dig in.

A violation record is a note that something about a merchant’s label billing did not follow the rules — the record keeps what type it was, a detail line that says what happened, and when it was recorded. The Violations page — LabelFlow → Violations (/labelflow/violations) — collects all of these records in one list, so when a merchant asks “what is this about?”, you can pull up the exact record instead of guessing. This page is for looking and checking: records are shown as they were recorded, and this article only covers what you can see and verify on the page.

Step 1: Read the two summary cards#

At the top of LabelFlow → Violations (/labelflow/violations), two cards sum up the list underneath: Violations (how many records the list currently shows) and Merchants involved (how many different merchants those records belong to). Read them together: ten records spread over eight merchants is a very different picture from ten records all belonging to one merchant. When you filter the list (next step), the cards follow the filtered list, so they always describe what you are looking at right now.

Step 2: Filter by merchant#

1. Open LabelFlow → Violations and pick a merchant in the filter at the top — the picker is searchable, so type part of the name if the list is long.
2. Click Search. The table now shows only that merchant’s records, and the two summary cards recount for that merchant alone.
3. Click Reset to clear the filter and return to all merchants’ records.

Step 3: Read each record#

• Merchant — whose record it is. If a merchant disputes a record, this column is how you confirm you are both looking at the same merchant’s history.
• Type — what kind of violation it was, in one short label.
• Detail — the line that says what actually happened for this record. Read it word for word before you answer anyone: it is the most specific information the page gives you.
• Time — when the record was created, down to the second. Use it to line the record up with the shipment or label from the same moment.

To check a record against the underlying label business, use the merchant, type and time you just read and look at the same merchant’s shipments in LabelFlow → Shipments (/labelflow/shipments) and its bought labels in LabelFlow → Labels (/labelflow/labels). The three pages tell one story from three sides: the shipment shows what was asked for, the label shows what was bought and charged, and the violation record shows what was flagged.

Watching for repeat records#

One record is an incident; the same type of record coming back for the same merchant is a habit worth a conversation. Use the merchant filter on LabelFlow → Violations (/labelflow/violations) to pull one merchant’s full list, then scan the Type column: if the same type keeps appearing, the merchant is repeating the same mistake, and fixing the habit stops future records at the source. The table shows 20 records per page, so page through before you conclude a merchant only has a few.

If a record does not look right#

1. Write down the record exactly as shown: merchant, type, detail and time. A dispute is only checkable if it points at one exact record, not at “some violation last month”.
2. Cross-check it with the shipment and label pages for the same merchant and time (previous section), so you can say what the shipment asked for and what the label charged.
3. Keep the merchant’s own explanation with those notes, so the record, the underlying shipment and the merchant’s side of the story stay in one place.

Docklify features used in this article#

• Violations list with Merchant, Type, Detail and Time columns — LabelFlow → Violations (/labelflow/violations)
• Summary cards: violation count and merchants involved — at the top of LabelFlow → Violations
• Merchant filter with Search and Reset — LabelFlow → Violations → filter bar
• Cross-check a record against its shipments — LabelFlow → Shipments (/labelflow/shipments)
• Cross-check a record against bought labels — LabelFlow → Labels (/labelflow/labels)