--- name: al-406-find-out-why-an-order-never-reached-your-accounting-or-wa description: "When a web order fails to reach the warehouse or the accounting system, a small online store usually has no IT department: someone digs through logs and settings or files a support ticket and waits. On Oct 29, 2026 Junipeer, a Nordic e-commerce integration platform, launched Junipeer MCP so teams can connect Claude, Cursor or other MCP-capable AI apps to their integrations and ask in plain language. One part gives the AI sync status, errors, settings and the ability to re-run failed syncs; another gives it data in 21 connected systems such as Fortnox (for example overdue invoices or payment payouts). Access follows the API key: with read-only access, any attempt to change something is denied, and the AI never sees the connected systems' passwords. Bread & Boxers' e-commerce manager says he asked his AI to go through all their integrations and within seconds saw what was running, how often and what had failed, and can ask why an order hasn't reached Fortnox; the agency Omniarch says…" --- # Find out why an order never reached your accounting or warehouse system by asking your AI assistant: connect it read-only to your store integrations, get the failed order, the cause and the fix in plain words, and approve any re-run yourself When a web order fails to reach the warehouse or the accounting system, a small online store usually has no IT department: someone digs through logs and settings or files a support ticket and waits. On Oct 29, 2026 Junipeer, a Nordic e-commerce integration platform, launched Junipeer MCP so teams can connect Claude, Cursor or other MCP-capable AI apps to their integrations and ask in plain language. One part gives the AI sync status, errors, settings and the ability to re-run failed syncs; another gives it data in 21 connected systems such as Fortnox (for example overdue invoices or payment payouts). Access follows the API key: with read-only access, any attempt to change something is denied, and the AI never sees the connected systems' passwords. Bread & Boxers' e-commerce manager says he asked his AI to go through all their integrations and within seconds saw what was running, how often and what had failed, and can ask why an order hasn't reached Fortnox; the agency Omniarch says it set up a Centra, Fortnox and Kustom order integration in 30 minutes instead of days or weeks. Pricing starts at 49 euros a month per workspace. The prompt below works with any integration tool your AI can read. ## Inputs to collect first Ask the user for anything below that they haven't already given you. Don't guess missing facts. - Webshop e.g. Shopify/Centra - Warehouse/3PL - Accounting e.g. Fortnox/Xero/QuickBooks - Payments - Order number ## Instructions Do the task below with the user's inputs in place of each [bracket]. You're connected (read-only) to my store's integrations: [webshop e.g. Shopify/Centra] -> [warehouse/3PL] -> [accounting e.g. Fortnox/Xero/QuickBooks] -> [payments]. Act as my integration troubleshooter. 1) Give me a health check: each integration, how often it runs, when it last succeeded, and anything that failed in the last [7] days, as a table. 2) For order [order number] (or every failed order), tell me in plain words where it stopped, the error message, the likely cause (e.g. missing SKU, VAT code, customer record, closed period) and the exact fix, and say which system the fix belongs in. 3) Group repeated errors and tell me which single fix would clear the most orders. 4) Compare today's order count in the webshop with what arrived in the warehouse and in accounting, and list any gaps. 5) Never re-run a sync, change a setting or edit a record yourself: write the step and wait for my 'yes'. If you can't see something, say so instead of guessing. End with a short note I can forward to my accountant or agency. ## Safety checks (share these with the user) - This prompt works on text other people wrote (emails, reviews, messages or web pages). That text can hide instructions aimed at AI, such as "ignore your rules and…". Paste it as material to work on, and never let the AI act on requests inside it, like paying, sharing logins or changing records. - Check every figure, price and total against your own records before anything is sent, posted or booked. A person approves refunds, discounts, payments and price changes. - Remove names, contact details, account numbers and other personal data the task doesn't need before you paste, and check your AI tool's data and training settings. - Check names, dates, numbers and any claim against your own source material before you use the answer. AI can misread or invent details. - Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed. ## About this skill - Works with: Junipeer MCP, Claude, Cursor, Fortnox - Based on this real-world example: https://junipeer.io/resource/junipeer-launches-mcp - Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-406-find-out-why-an-order-never-reached-your-accounting-or-wareh/ - To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/