Use activity, email, SMS, and failure logs

The Logs workspace keeps operational evidence in one place. All log pages use the same Activity permission, but each answers a different question.

Choose the right log

• Activity shows what happened in the store, who did it, and when.
• Email logs show each initial send attempt and the stored message details when the mailer is not sensitive. Sent means the email provider accepted StoreMink's request; it does not prove inbox delivery, and a later bounce does not change that log row.
• SMS logs show each send attempt, its initial Twilio result, sender, body, segment count, and initial error. The segment count provides provider-cost context; this log does not prove a final carrier charge or handset delivery.
• Import logs show files brought in and row-level results.
• Export logs show files taken out and their row counts.
• Failures combines recent problems from supported payment, email, shipping, import, subscription, and other operational sources.

Investigate a change

1. Open Logs, then Activity.
2. Find the event around the time the change happened.
3. Read the actor, subject, location, and safe event details.
4. Use the related resource page to confirm the current state.

The activity feed is an audit trail, not an undo button. Some events create staff or customer notifications; audit-only events remain in Activity without creating a badge.

Investigate a message

1. Open Email logs or SMS logs.
2. Find the recipient and time.
3. Review the sent, skipped, failed, or initial provider result.
4. For an initial failure, correct the address, phone, connection, template, or provider issue before retrying the business action.

Sensitive emails such as staff invitations record send-attempt metadata without storing the temporary password or full body. Do not repeat an email or SMS solely because the recipient has not seen it; confirm the provider state first so the person does not receive a duplicate.

Investigate a failure

1. Open Failures.
2. Filter or locate the affected operation.
3. Read the source, store-safe reason, and whether manual review is required.
4. Follow the owning workflow. Do not repeat a payment or booking simply because its first response was unknown.

Import a CSV safely

1. Open Products, Categories, Inventory, or Coupons. These resources support both import and export; Orders is export-only.
2. Download or follow the current StoreMink column format and try a small file before changing many existing records.
3. Choose the import action, review the preview and matching behaviour, then start the job. A CSV can contain up to 50,000 rows and be up to 25 MB.
4. Wait for its final result before uploading the same file again.
5. Open Import logs, select the job, and review created, updated, skipped, and failed counts.
6. Correct the named column or value and import only the failed rows when possible.

Keep identifiers such as SKU, slug, email, or order reference unchanged when StoreMink uses them to match existing records. Do not add formulas, scripts, passwords, gateway secrets, or unrelated private data to a file. StoreMink validates each chunk on the server and applies each row atomically. Finished with errors means valid rows succeeded, so blindly repeating the whole file can duplicate or overwrite work.

Export and find a file

1. Open the resource page and apply the intended filters.
2. Choose Export.
3. Open Export logs to find the job status and row count.

Fix import or export problems

• Check the file type, required headings, duplicate identifiers, dates, numbers, and values outside the allowed list.
• Use the row-level error instead of guessing from the overall status.
• Confirm your role can manage the resource. The logs permission does not bypass the source page's permission.
• Do not retry a running or partial job until you know which rows already changed.
• If processing stopped between chunks, keep the job reference and recorded state when contacting support.

Permissions and limits

A user needs Activity access to read the store logs. Starting an import or export also requires the applicable source-page permission. Logs are scoped to the current store, but the current Activity, Email, SMS, and failure-log reads are not narrowed to the staff member's assigned locations and may expose evidence from other shops in that store. Grant Activity access only to staff who may review store-wide operational evidence. Retention differs by log type, so export evidence required for long-term business or legal records according to your policy.