Skip to main content

Activity logs and troubleshooting

Watch the activity log tour

The clip covers the full Logs / Activities experience (you may also have seen Recent activity on the Dashboard—that is a digest; here you get searchable history across domains). Tabs, grids, statuses, references, and how support uses the same timeline to narrow issues quickly. Turn on audio if your device supports it.

Download MP4 · Download original MOV · Same tour as above; MOV is the source export.

Understand your activity timeline

The Activities screen (often Activities or Logs) gives shop admins—and the support teams assisting them—transparent visibility into what happened and when across the B2B Plus app. Rows span orders, inventory, customers (including company or location syncs when logged), settings, spreadsheet uploads, sales rep import history, webhooks, and related jobs so you can validate successes, spot failures, and investigate broader change windows before or after something looks wrong in operations.

That same clarity helps support triage merchant issues faster: share timestamps, status and category badges, and reference IDs from a row to shorten back-and-forth and speed resolution.

Dashboard vs this page: Recent activity on the Dashboard is a short live digest from the same underlying log stream; Activities / Logs here is the full, searchable timeline for deeper work.

Use it to answer what changed?, copy identifiers into tickets, and pair with Upload History (see Filter tabs) plus Inventory upload tooling when imports only partly succeed.

Activities page layout

The screen is built around filter tabs and a searchable activity grid. Each row is one recorded event with status, category, optional reference links, timing, and owner (who or what triggered it).

B2B Plus Activities: tabs All Orders Inventory Customers Settings Upload History Rep Import History, activity grid with status and category badges

Filter tabs

Tabs narrow the list by the area of the product the event belongs to:

TabTypical use
AllEvery activity type in scope—best for broad investigation.
OrdersOrder updates, webhooks, fulfillment-related messages, and similar.
InventoryInventory syncs, uploads, planning, and stock-related jobs.
CustomersCustomer syncs, profile changes, and buyer-related events.
SettingsShop configuration changes when your app logs them.
Upload HistorySpreadsheet import jobs (for example inventory CSV) and outcomes.
Rep Import HistorySales rep CSV or bulk import activity.

Exact tab labels can vary slightly by version; use All first if you are unsure which tab holds an event.

Search and filters

On the right above the grid you usually see search and filter controls. Combine these with a tab and (when available) date or status filters to avoid scrolling through very large bulk-job periods.

Columns on the activity grid

ColumnWhat it shows
ActivityA short title (bold) plus a longer description with context—identifiers, company names, counts synced, webhook names, etc.
StatusOutcome badge—for example Success (green). Failed or warning states may appear in other colors when something needs attention.
CategoryEntity type badge such as COMPANY, CUSTOMER, LOCATION, or ORDER (colors follow your theme).
ReferenceClickable ID or link when the event ties to a specific record (order id, customer id, etc.). Shows when there is no single reference.
DateOften two lines: a relative time (e.g. “21 hours ago”) and an absolute date/time (e.g. “May 14, 2024, 01:29 PM”).
OwnerWho or what triggered the action: a user (name and email), a system label (e.g. webhook-driven text), or for unattended sync jobs.

Examples of what you might see

  • Company switch via theme — Storefront company context change, sometimes with location/company identifiers in the description.
  • Customer sync completed / Location sync completed — Bulk sync summaries (counts synced or ignored).
  • Order updated via webhook — Changes driven by Shopify or middleware webhooks; owner may read like a webhook source rather than a person.
  • Representative assigned — Rep linked to a company, with company name and rep email in the details.

Use the Category and Reference columns to jump from an event to the right area of Orders, Customers, or Sales reps when your UI links them.

Business purpose

  • Give store staff and support a single pane to see both successful automations and failures tied to real references (IDs, links) instead of reconstructing history from memory.
  • Answer “what changed?” during busy seasons or after bulk jobs—from settings flips to webhook-driven order updates.
  • Equip partner and internal support so they can narrow tickets quickly and often resolve issues faster using the same exported context merchants see.
  • Supply lightweight governance evidence for sensitive configuration or integration touches.

Step-by-step usage

Browse activities

  1. Open Activities (or Logs) from the app navigation.
  2. Pick a tab (for example Upload History for imports, Orders for webhook noise).
  3. Use search and filters to narrow by date, status, text in the activity title or description, or reference—depending on what your deployment exposes.
  4. Open reference links when present to jump to the related Shopify or app record.

Investigate uploads

  1. Switch to Upload History (or filter category to upload-related events).
  2. When offered, download failed rows as CSV for correction.
  3. Fix the source spreadsheet and re-upload from Inventory or your integration path.

Partner escalation checklist

Before contacting B2B Plus support, gather what they can match against Activities:

  • Approximate timestamp and shop name
  • Tab and filters you used
  • Whether a bulk job was running
  • Any reference IDs visible in the grid
  • A screenshot of the activity row if helpful

Including those items mirrors how support teams typically narrow issues with brands—often leading to quicker answers than screenshots of symptoms alone.

Important notes

  • Activities are application-level audit entries—they complement but do not replace Shopify’s own order timeline for every Shopify-native event.
  • Large bulk operations may produce many rows—always narrow by tab and date first.
  • Owner may be blank for system automation; that does not mean the event is unimportant.

Limitations

  • Retention duration depends on your deployment and hosting policies—confirm with your administrator.
  • Some low-level infrastructure logs are not shown to merchants.

FAQs

Can I delete log rows?
Usually no—they are protective records.

Why don’t I see a webhook entry?
Shopify must deliver the webhook and your job must record it—timing issues or disabled topics can cause gaps.

Troubleshooting

SymptomSuggested action
Inventory diverged after overnight syncUse Inventory tab or All; look for sync or webhook failures; re-run uploads if needed.
Settings changed unexpectedlyFilter Settings (or All) around the time of change; restrict who can edit Settings.
ERP or API failuresSearch descriptions for API or export errors; involve integration owner with reference IDs if logged.
Import partially failedOpen Upload History; download failed rows; fix and re-upload.