Skip to main content

Evidence and sale progress

Evidence supports the sale's configured checks. Supplying a file is one part of the workflow; it does not automatically confirm payment, qualify the sale or release earnings.

Evidence and sale progress — operations maker
Example screen: operations maker. Local sample data; records and available actions depend on your access. Open desktop image · Open mobile image.

Add evidence​

  1. Enter non-file evidence during capture. For files, save the draft, open its sale details and select Attach evidence.
  2. Identify the required evidence type. Rules may ask for a file, provider reference, customer acknowledgement, location, timestamp or field value.
  3. Enter the real business information or choose the configured Type of proof, approved document processing purpose and relevant file. Keep evidence linked to the correct sale.
  4. Wait for file upload and scanning to finish. Follow file guidance if a file is rejected or still pending.
  5. Submit the evidence action and check the resulting record or status.

Location coordinates have defined ranges: latitude from −90 to 90, longitude from −180 to 180. Accuracy, when supplied, cannot be negative. Do not replace a real location with an example from this guide.

Read progress as separate checks​

The detail screen can show different dimensions of progress. Payment, qualification and fulfilment can change at different times. Look for missing evidence, unmatched payments, unmet conditions or case holds rather than assuming that one successful step completes all others.

Use the fulfilment action only when the underlying delivery or service event has occurred. Use cancellation only when appropriate for the record's state. After a sale has progressed financially, a refund or return may be the relevant workflow instead.

For an accepted physical sale, an authorized stock custodian uses Record fulfilment, enters the quantity Delivered now for each product and supplies a delivery reference. The form defaults to the remaining quantity; reduce it for a partial handover, or use 0 for a product not handed over. Do not exceed the remaining quantity. Successful handover updates delivered quantities; capturing or paying for a sale alone does not mark its stock delivered. Returns use the refund/custody workflow rather than negative delivery quantities.

Physical handover requires positive incremental quantities for at least one line. Serialized units must be whole numbers. The form derives full or partial fulfilment from all delivery-required lines, and a pending physical delivery cannot be recorded as an empty successful event. The API checks the sale state, remaining quantities and the custodian's campaign authority again on submission.

Safaricom quality qualification is a separate event. Upload the original provider report against its campaign, retain the provider column names and serials as text, review the check-only results and apply the report using its genuine delivery reference. A matched, eligible SIM with Quality=Y qualifies at successful ingestion time. A file attachment or manual delivery record is not a substitute for that provider result. Stock handover remains necessary independently of payment and qualification.

If a request times out, keep this form open and retry the unchanged action so its operation ID is reused. Do not record the same handover under a new reference simply because the response was lost. A definite validation rejection can be corrected and submitted as a new operation.

Recover from a problem​

If the record changed while you were working, close the action, refresh and review the latest details before retrying. If the evidence file is still scanning, it is not ready to be used as clean evidence. If a permission is missing, ask an administrator for the specific task you need to perform.

For a sale that remains unqualified, inspect the configured requirements and imported verification results. Do not change product rules merely to bypass a failed check.