Stark Consultancy

Orders & inventory · 05 / 20

Sales order intake & validation

Twelve rules fire on every incoming order batch before an SO ID is ever created.

Sample data · synthetic

What actually changes

Stop bad orders from ever reaching the warehouse floor.

Orders with wrong pincodes, blocked customers, or stale prices slip through and only get caught after picking has started.

Catch every one of twelve order defects before an SO ID is even created
See exactly which rule failed on which row instead of guessing why an order got stuck
Fix and rerun a whole batch in one pass instead of chasing corrections order by order

What was built

A validation engine: twelve rules, a fix-and-rerun loop, and generated SO IDs for clean rows.

Result

12

validation rules, one pass

The mechanics

How this actually runs, step by step.

  1. 1An incoming order batch is loaded as raw rows, exactly as received.
  2. 2Twelve rules run against every row, independently, so one failure doesn't block the others.
  3. 3Failing rows land in an error table with the specific rule that failed.
  4. 4Fixing one error class and re-running clears just those rows — not the whole batch.
  5. 5Rows that pass every rule get a generated SO ID.
Rule engineSKU masterPincode master