SATIK DEVELOPER DOCS · V1 BETA
A verdict you can explain.
No mystery score. A decision, reasons, and one next step.
Compare the verdicts
Use the verdict together with its reasons and recommended next step.
| Verdict | Meaning and next step |
|---|---|
Ready to shipSHIP | The address is complete and validated to a building or sub-premise, with no rule requiring extra attention. No history is informational and does not block shipping. |
Review a detailREVIEW | A correctable issue needs attention: a missing unit, inferred detail, changed pincode, street-level precision, or sufficient adverse delivery history. |
Verify before dispatchVERIFY_FIRST | The address cannot be reliably located, is incomplete, contains suspicious locality or pincode details, or has sufficiently adverse unit-level outcomes. Contact the customer before dispatch. |
No numeric deliverability score
A calibrated delivery probability requires real outcome evidence. Satik beta deliberately returns deterministic rules and their traces.
Recommended actions and verdicts
recommended_action tells your operations team what to do next; it does not automatically dispatch a parcel or contact a customer. These are all eight allowed values and their possible final verdicts under the current rules. Read the action together with verdict, flags, and rule_trace.
| Recommended action | Possible verdict | Meaning |
|---|---|---|
Dispatch normallySHIP_AS_IS | SHIP | Proceed with normal dispatch checks. This is not a delivery guarantee. |
Confirm the pincodeCONFIRM_PINCODE | REVIEW or VERIFY_FIRST | Confirm the postal code with the customer. |
Ask for the unit numberREQUEST_UNIT_NUMBER | REVIEW | Ask for the flat, house, or shop number, or building details. |
Ask for a landmarkREQUEST_LANDMARK | REVIEW | Ask for a useful, specific landmark. |
Confirm address correctionsCONFIRM_CORRECTIONS | REVIEW | Ask the customer to confirm inferred or corrected address details. |
Review manuallyMANUAL_REVIEW | REVIEW | Have an operator inspect the address and its verification result. |
Request the full addressREQUEST_FULL_ADDRESS | VERIFY_FIRST | Request the complete delivery address. |
Contact the customerCALL_CUSTOMER | VERIFY_FIRST | Contact the customer to clarify the address before dispatch. |
Why one action can accompany two verdicts
CONFIRM_PINCODE accompanies REVIEW when the provider replaced the postal code (rule 4), or VERIFY_FIRST when locality or postal code details are suspicious (rule 3). History rules can subsequently override both verdict and action. Use the final response fields for your workflow; the rule trace explains how the decision was reached.
| Guide | What you will learn |
|---|---|
| Rule trace | Conditions, rule priority, and history overrides behind each verdict/action pair. |
| Dispatch playbook | Example customer questions and how to verify a corrected address. |