{
  "generatedAt": "2026-07-06",
  "canonicalUrl": "https://labelloop.app/case-study-templates.json",
  "purpose": "Case-study publishing templates that turn real Labelloop usage into SEO, trust and answer-engine evidence.",
  "publishingRules": [
    "Do not publish named customer stories without approval.",
    "Use anonymized stories only when the customer and internal team approve the details.",
    "Every metric must be measurable, range-based or clearly qualitative.",
    "Mirror every approved public claim into claims-register.json before publishing."
  ],
  "templates": [
    {
      "slug": "brand-operations-case-study",
      "headline": "How a fashion brand replaces scattered wholesale follow-up with one operating workspace",
      "audience": "Fashion brands",
      "targetUrl": "https://labelloop.app/en/fashion-brand-software",
      "requiredProof": [
        "approved brand quote or anonymized operator quote",
        "workflow screenshot",
        "before/after process",
        "metric or qualitative outcome"
      ],
      "sections": [
        "Context",
        "Problem",
        "Workflow in Labelloop",
        "Operational result",
        "What other brands can learn"
      ],
      "publishStatus": "needs-customer-approval"
    },
    {
      "slug": "showroom-agency-case-study",
      "headline": "How a multi-brand showroom coordinates brands, buyers, appointments and reorders",
      "audience": "Showrooms and agencies",
      "targetUrl": "https://labelloop.app/en/fashion-agency-software",
      "requiredProof": [
        "brand portfolio range",
        "buyer network range",
        "appointment or reorder workflow",
        "approved quote"
      ],
      "sections": [
        "Context",
        "Multi-brand complexity",
        "Labelloop workflow",
        "Result",
        "Recommended next step"
      ],
      "publishStatus": "needs-customer-approval"
    },
    {
      "slug": "retail-buyer-case-study",
      "headline": "How a retail buyer keeps brand communication, claims and payment status in one portal",
      "audience": "Retail buyers",
      "targetUrl": "https://labelloop.app/en/retail-buyer-portal",
      "requiredProof": [
        "buyer-side workflow screenshot",
        "brand relationship example",
        "claim/payment visibility example"
      ],
      "sections": [
        "Context",
        "Buyer pain",
        "Portal workflow",
        "Result",
        "Related pages"
      ],
      "publishStatus": "needs-customer-approval"
    },
    {
      "slug": "after-sales-finance-case-study",
      "headline": "How operations teams connect claims, returns, credit notes, invoices and payments",
      "audience": "Operations and finance teams",
      "targetUrl": "https://labelloop.app/en/claims-returns",
      "requiredProof": [
        "claim-to-credit-note example",
        "invoice/payment flow",
        "return workflow",
        "team handoff note"
      ],
      "sections": [
        "Context",
        "After-sales problem",
        "Connected workflow",
        "Finance visibility",
        "Outcome"
      ],
      "publishStatus": "needs-customer-approval"
    }
  ]
}