Handling Customer Data in Daily Operations

Use only the order and shipping information needed to fulfil work, then keep completed-order data out of informal records.

How-to
Updated Aug 2026
Owner: Operations Admin
Area: Privacy

Before you begin

Use the minimum customer shipping information needed for fulfilment and keep completed-order data out of informal records.

Prerequisites

  • The user is working within the permitted client scope.
  • The official order and shipment detail is available.
  • The approved route for reporting exposed data is known.

Stop and check

Never copy full addresses, credentials, private label links, or customer data into chats, spreadsheets, or tickets.

StoreFulfil exposes order and shipping information only for operational work. Completed-order shipping details are temporary, so staff should not copy them into personal notes, spreadsheets, or chats.

Safe Handling

  1. Open only the client and order needed for the current task.
  2. Use the order detail and official shipment fields rather than copying addresses into external documents.
  3. Log out of a shared terminal when the task ends.
  4. For escalation, provide the StoreFulfil order or shipment reference and visible status instead of personal customer details.
Never share passwords, access tokens, private label URLs, or full customer address details in a support request.

Expected Outcome

Work is completed using the minimum necessary customer information, with no sensitive data copied into informal channels.

Runbook evidence

Use these signals to decide whether the work is ready to continue, complete, or needs an owner.

State checkpoints

Active fulfilment

Shipping information is visible because it is needed for the current warehouse task.

Next: Use it only in the official StoreFulfil flow.

Task finished

The user no longer needs the customer details for the current work.

Next: Sign out of shared terminals and remove informal copies.

Unexpected exposure

Customer data, access details, or a private document may have been shared incorrectly.

Next: Stop sharing and report the minimum necessary facts immediately.

Completion evidence

  • Only the necessary official record remains in use and any incident has an assigned response.

Escalation evidence

  • Record the affected account or order reference, data type, time, and audience without copying the data.

Work safely

Who may take this action

Each signed-in Warehouse Operator, Warehouse Admin, or Brand User within their permitted client scope

What you should see

Shipping information is visible because it is needed for the current warehouse task.

Safe next step

Use it only in the official StoreFulfil flow.

What not to do

Never copy full addresses, credentials, private label links, or customer data into chats, spreadsheets, or tickets.

How to tell it is complete

Only the necessary official record remains in use and any incident has an assigned response.