ERP Export Alerts and Retries
- Home dashboard: Administrators see failed ERP exports and eligible orders awaiting export in Needs attention. Each alert opens its filtered Order delivery queue. Counts refresh every minute while the dashboard is open and with Refresh. Unpaid orders are not counted as failed exports.
- Retry ERP sync: For a paused failure, resolve the recorded cause, choose Retry ERP sync, and confirm that the order is not already in ERP. The command clears the failure counter so the existing scheduler can try again. Retry queued is not confirmation of ERP delivery. The previous error and administrator are recorded in the audit trail.
- Already scheduled: Orders below the three-failure pause remain eligible for the next scheduler cycle. Refresh reads status; it does not force an extra export or reset an active attempt.
- Do not duplicate orders: An unknown ERP outcome requires reconciliation through ERP services. The retry endpoint refuses these orders, acknowledged exports, unpaid card orders, and orders outside your permitted brands.
- Failure feedback: A rejected retry keeps the confirmation and error visible. Cancel sends no request. An unavailable dashboard queue is not an all-clear result.
Dashboard Overview
Purpose: Start your session with the work that needs you, the key figures of your workspace, storefront traffic, and a direct path to the most common tasks.
What You Can Do Here
- Read the summary: The greeting line tells you how many tasks are waiting; select the count to jump to the Needs attention card.
- Use quick actions: Create a page, article or product, or open the media library, orders and support inbox. Only actions you are allowed to perform are shown.
- Clear the Needs attention card: The purple card lists content awaiting approval, rejected items, new inquiries, orders awaiting processing and low-stock products. Select a row to open the relevant queue; queues that are clear appear as green ticks, and an "all caught up" message appears when nothing is waiting.
- Read the key figures: Products, Orders (with a 14-day sparkline and week-over-week change), Revenue over the last 30 days compared with the previous 30 days, and Low stock. Each tile opens the matching list page; tiles you cannot access are hidden.
- Follow storefront traffic: Page views and visitors for the last 7 days versus the previous week, a 14-day chart and the most viewed pages (each opens the live page). Open analytics leads to the full Analytics page.
- Review recent activity: The five newest orders open their order detail, and the newest unread inquiries open the support inbox.
- Act on rejected content: Rejected items show the reviewer's reason and an Edit & Resubmit link.
- Open detailed reports: The Analytics Center card is collapsed by default; choose Show reports for audience, content, catalog, engagement and acquisition views with CSV export.
- Refresh: Use the Refresh button or Ctrl+R to reload every figure you are authorized to see.
Key Concepts
- Permission-aware widgets: Every card, tile and panel is filtered by your role and permissions; no data is requested for areas you cannot open.
- Pending orders: Orders in Submitted, Confirmed or Processing status that still require back-office handling.
- Revenue: Total of non-cancelled orders in the currency with the most orders over the last 60 days; other currencies are not mixed into the figure.
- New inquiries: Storefront contact or product inquiries that nobody has opened or replied to yet.
- Unavailable: A tile or panel shows this when its service did not respond; use Retry or Refresh once the service is reachable.
When an Action Fails
- Read the error: Request failures show a notification with the available reason. Shared error notifications remain until you close them; closing a notification does not undo an operation.
- Correct and retry: Check the highlighted fields or page error, keep your edits, and retry once the issue is corrected.
- Check partial completion: If a document was created but its product links failed, open that existing entry in the Document Library to repair the links. Do not create or upload the document again.
- Check connection failures: When the server response is lost, verify the current record before retrying a write. The operation may already have completed.
When a Page Cannot Be Displayed
- Recover the page: Use Retry for a page error. If page files could not be loaded after an update or connection interruption, use Reload Page to request the current files.
- Continue elsewhere: Use the sidebar, Go Back, or Dashboard. Navigation clears the previous page error; a failure on one page does not block another page.
- Check your work: Unsaved changes on the failed page may be lost. Verify the current record before repeating a save or other write.
- Report a recurring error: Open Technical details and select Copy details. Share the page, time, support reference, and error message with support. If copying is unavailable, select the visible details manually.