Skip to main content
Challenge

Build a Return Proof Evidence Reconciler and Seller Response Assembler

Cross-reference buyer damage evidence against courier delivery logs and seller packaging manifests. Synthesize structured dispute response dossiers for Beckn arbitration.

Workflow AutomationHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Cross-reference buyer damage evidence against courier delivery logs and seller packaging manifests. Synthesize structured dispute response dossiers for Beckn arbitration.

E-commerce seller dispute specialist

Ingest contested buyer return claims and attached synthetic photo metadata from Beckn callbacks.

Compare delivery timestamp signatures against original courier proof-of-delivery records.

Evaluate seller pre-shipment packaging weigh-in logs against claimed transit damage patterns.

Assemble an objective dispute response dossier with recommended settlement terms for seller review.

Split-screen evidence comparator showing pre-shipment weights, delivery photos, and draft Beckn response.

Synthesize paired pre-shipment warehouse logs, proof-of-delivery telemetry, and buyer return files. Starter examples below are synthetic. They are not downloaded records.

Beckn protocol specifications Adopts Beckn Core 1.0.0 post-fulfillment feedback, dispute response, and callback message structures.

crewai, pydantic, fastapi. Orchestrates specialized agent roles for courier audit, packaging analysis, and legal dispute drafting. Local Llama 3 or hosted Claude model for dispute evidence extraction and response generation.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Match return claims against courier tracking events and pre-dispatch weight manifests.

Calculate dimensional and weight discrepancies to detect transit tampering.

Generate compliant Beckn response payloads containing dispute evidence attachments.

Require merchant dispute specialist authorization before transmitting responses.

```json [ { "input": { "dispute_id": "DISP-552", "buyer_claim": "Received empty box without high-value silk sari", "dispatch_weight_kg": 1.25, "delivery_weight_kg": 0.35, "carrier_seal_intact": false }, "expected_output": { "tampering_detected": true, "liability_assignment": "LOGISTICS_PROVIDER", "seller_reimbursement_eligible": true, "recommended_settlement": "FULL_BUYER_REFUND_VIA_CARRIER_INSURANCE", "beckn_status": "dispute_rebuttal_drafted" } }, { "input": { "dispute_id": "DISP-881", "buyer_claim": "Broken ceramic bowl inside sealed container", "dispatch_weight_kg": 2.1, "delivery_weight_kg": 2.1, "carrier_seal_intact": true }, "expected_output": { "tampering_detected": false, "liability_assignment": "SELLER_PACKAGING", "seller_reimbursement_eligible": false, "recommended_settlement": "SELLER_REPLACEMENT", "beckn_status": "dispute_accepted" } } ] ```

Maintains mock dispute proceedings; does not issue financial debits or make binding judicial rulings. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Maintains mock dispute proceedings; does not issue financial debits or make binding judicial rulings. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Match return claims against courier tracking events and pre-dispatch weight manifests. Calculate dimensional and weight discrepancies to detect transit tampering. Generate compliant Beckn response payloads containing dispute evidence attachments. Require merchant dispute specialist authorization before transmitting responses.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest contested buyer return claims and attached synthetic photo metadata from Beckn callbacks. Compare delivery timestamp signatures against original courier proof-of-delivery records. Evaluate seller pre-shipment packaging weigh-in logs against claimed transit damage patterns. Assemble an objective dispute response dossier with recommended settlement terms for seller review.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Match return claims against courier tracking events and pre-dispatch weight manifests. Calculate dimensional and weight discrepancies to detect transit tampering. Generate compliant Beckn response payloads containing dispute evidence attachments. Require merchant dispute specialist authorization before transmitting responses.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Split-screen evidence comparator showing pre-shipment weights, delivery photos, and draft Beckn response.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Maintains mock dispute proceedings; does not issue financial debits or make binding judicial rulings.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest contested buyer return claims and attached synthetic photo metadata from Beckn callbacks.

  • Compare delivery timestamp signatures against original courier proof-of-delivery records.

  • Evaluate seller pre-shipment packaging weigh-in logs against claimed transit damage patterns.

  • Assemble an objective dispute response dossier with recommended settlement terms for seller review.

Resources and assets

Reference links and supporting material

Dataset notes

Synthesize paired pre-shipment warehouse logs, proof-of-delivery telemetry, and buyer return files. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

crewAI

Multi-agent orchestration framework

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest contested buyer return claims and attached synthetic photo metadata from Beckn callbacks. Compare de...
  • Match return claims against courier tracking events and pre-dispatch weight manifests. Calculate dimensiona...
  • Split-screen evidence comparator showing pre-shipment weights, delivery photos, and draft Beckn response.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • crewAI · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Return Proof Evidence Reconciler and Seller Response Assembler