A wholesale customer says an order no longer qualifies for checkout. Before changing the minimum again, preserve what happened, check the actual rule and give the next reviewer a clear record.
This is an evidence and troubleshooting workflow, not advice about which commercial minimum your business should choose. The example is fictional. Logged.ai does not automatically capture every third-party wholesale plugin’s settings.
Start with the change you can describe
Write down the affected site, the approximate time, the customer-visible result and one example that reproduces it. “A returning wholesale account with the same basket now sees a minimum-order message” is more useful than “checkout is broken.”
Record the site’s time zone and the time shown in your evidence. Avoid pasting customer names, addresses, payment information or session cookies into review notes.
Preserve the rule before editing it
Open the wholesale plugin’s own configuration with an authorized account. Record the relevant rule, its scope and the expected result. Preserve an appropriately redacted screenshot or an export the rule provider supports.
A Logged.ai activity record is not a backup of an arbitrary plugin’s settings. If this exact configuration change is outside the documented collectors, keep that limitation explicit. Do not turn a missing event into a claim that nobody changed the rule.
Find the surrounding recorded changes
In Logged.ai → Activity, start with a narrow time window and the relevant site. Review supported plugin, user, product or store changes that could explain the symptoms. Expand the period only when you need more context.
Open a record and distinguish the acting account, affected object, recorded outcome and available before/after values. A staff account, scheduled task or unknown actor describes the recorded context; it does not by itself identify a person or establish intent.
Check coverage and health
If the expected event is absent, check filters, retention, collection settings and System status. Collection begins when enabled; it cannot reconstruct older actions. A cache, CDN or server can also handle a request before WordPress observes it.
Check what persisted
Compare the rule’s current value with the actual shopper result. A nearby product change may be relevant without being the cause. Test the basket, customer role and site scope that reproduce the problem rather than inferring the result from a timestamp alone.
Keep a small evidence export
Use Reports & exports to preserve a focused selection. CSV is convenient for a spreadsheet; JSON keeps a structured representation. Free includes on-demand exports. A direct download must fit the complete-selection limit of 1,000 records and 2 MiB; narrow the period if it does not.
Read the end-date explanation: a “before” timestamp excludes records at that exact instant. Store the export privately and share only what the next reviewer needs.
Test one proposed correction
Use a staging copy and a fictional basket. Record the expected result, make one reversible change, repeat the same steps and record the outcome. Include a control basket that should remain unaffected. Confirm the rule in the wholesale plugin itself.
Logged.ai can help you review supported recorded changes around the test. It does not decide the right minimum, prove the commercial calculation or certify every integration.
Hand over a decision, not a pile of screenshots
Free can provide the filtered activity and export. In Pro, Cases & handover keeps related retained evidence, review notes, decisions and the next owner together. Summarize what was observed, what remains uncertain, the test result and who will verify the next step.
When a recurring check is useful, Pro’s saved searches and scheduled reports can support it. Creating a case or reading a preview does not automatically enable an alert, schedule or response.
Continue with finding a recorded change, exporting a useful evidence slice or working through a case.
