Logs
The Logs section gives admins visibility into what yStore is doing behind the scenes. Use logs to debug issues, monitor integrations, and audit store activity.
Navigate to yStore → Logs in the CP.
The Logs section is only visible to users with admin privileges in Craft CMS.
Log types
yStore maintains several separate log streams, each accessible from a tab in the Logs screen:
Order Logs
Records every order status change, method update, and system action taken on an order.
Useful for: Tracing why an order changed status, debugging order sync issues.
Fields: Order number, event type, message, timestamp, source (customer / admin / system).
Payment Logs
Records every payment gateway interaction — initiated, authorized, captured, failed, refunded.
Useful for: Diagnosing failed payments, confirming gateway callbacks were received.
Fields: Order number, payment method, gateway response code, status, amount, timestamp.
If a customer reports a payment failure, check Payment Logs first. The gateway response message usually tells you exactly what went wrong (insufficient funds, 3DS failure, card expired, etc.).
Email Logs
Records every transactional email attempted — confirmation, status change, password reset, marketing.
Useful for: Confirming emails were sent, debugging delivery issues, checking template rendering errors.
Fields: Recipient, subject, template used, sent/failed status, timestamp.
Automation / Flow Logs
Records every marketing flow execution — which trigger fired, which actions ran, success/failure per step.
Useful for: Debugging automation flows, verifying abandoned cart reminders triggered, checking flow conditions.
Fields: Flow name, trigger, execution status, step results, timestamp.
See Marketing → Flow Manager for flow setup.
Analytics Logs
Records store analytics events — product views, add-to-cart, searches, purchases.
Useful for: Verifying analytics collection is working, checking event payloads.
Analytics logs require the Enterprise edition.
System / Error Logs
Records plugin-level errors, exceptions, and warnings.
Useful for: Debugging plugin issues, finding PHP errors that don't appear in Craft's main log.
Fields: Error level (error/warning/info), message, stack trace (when available), timestamp.
Import / Sync Logs
Records results of product import, order fetch, and store synchronization operations.
Useful for: Diagnosing sync failures, verifying import row counts, checking skipped records.
Using the log viewer
- Go to
yStore → Logs. - Select the log type tab.
- Use the date filter to narrow the time range.
- Use the search to find specific order numbers, email addresses, or error messages.
- Click any row for the full log entry detail.
Clearing logs
Log entries are not automatically purged. To clear old log data:
# View available reset commands
php craft help yui/reset
Log clearing is permanent. Export logs to a file before clearing if you need an audit trail.
Log retention recommendation
For production stores, consider setting up a cron job or database maintenance routine to archive logs older than 90 days. High-traffic stores generate significant log volume.