@aglyn/aglyn 1.0.0-beta.255 → 1.0.0-beta.257

package/src/lib/app-utils/docs-index.generated.js

@@ -1766,7 +1766,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Element catalog',
         heading: 'Forms',
         anchor: '#forms',
-        text: 'Forms and their fields, covered in full with the feature they belong to — see Forms.\nA Form holds the fields and sends them. Each field is built from separate elements, so every piece can be selected and styled with the Styles panel on its own:\n| Element | What it\'s for |\n| Form Control | One field\'s frame: holds its Form Label, input and Helper Text. |\n| Form Label | The words naming a field, above its input. |\n| Input | A box to type in — Text, Email, Phone, Link or Number, one line or several. |\n| Helper Text | A line of guidance under a field. |\n| Select / Select Option | A dropdown and its choices. |\n| Checkbox | A tick box. Several sharing one Field name are one multi-choice question. |\n| Radio Group / Radio | A set of choices of which one may be picked. |\n| Choice Label | The words beside a Checkbox or Radio placed inside it. |\n| Rating | Stars a visitor picks. |\nThe group\'s presets put these together: Text field, Email field, Message field, Dropdown field, Radio choice field, Checkbox, Rating field and Helper Text, plus Contact Form, Contact Section and Marketing consent. Every setting is described under Field types; to design the button yourself, see Style a field.'
+        text: 'Forms and their fields, covered in full with the feature they belong to — see Forms.\nA Form holds the fields and sends them. Each field is built from separate elements, so every piece can be selected and styled with the Styles panel on its own:\n| Element | What it\'s for |\n| Form Control | One field\'s frame: holds its Form Label, input and Helper Text. |\n| Form Label | The words naming a field, above its input. |\n| Input | A box to type in — Text, Email, Phone, Link or Number, one line or several. |\n| Helper Text | A line of guidance under a field. |\n| Select / Select Option | A dropdown and its choices. |\n| Checkbox | A tick box. Several sharing one Field name are one multi-choice question. |\n| Radio Group / Radio | A set of choices of which one may be picked. |\n| Choice Label | The words beside a Checkbox or Radio placed inside it. |\n| Rating | Stars a visitor picks. |\n| Date Picker / Time Picker | A date picked from a calendar, or a time picked from a clock. |\nThe group\'s presets put these together: Text field, Email field, Message field, Dropdown field, Radio choice field, Checkbox, Rating field, Date field, Time field and Helper Text, plus Contact Form, Contact Section and Marketing consent. Every setting is described under Field types; to design the button yourself, see Style a field.'
     },
     {
         path: '/building-sites/besigner/element-catalog',
@@ -4531,14 +4531,14 @@ export const DOCS_SECTION_INDEX = [
         title: 'Fulfillment networks (ShipBob, ShipMonk and Amazon MCF)',
         heading: 'Connect a network',
         anchor: '#connect-a-network',
-        text: '1. Open Products → Shipping & delivery and find the Fulfillment networks card.\n2. Next to ShipBob or Amazon Multi-Channel Fulfillment (when the card offers them), select Connect.\n3. Sign in to that account and allow Aglyn access. You come back to the store settings with the network connected.\nYou need to be an admin of the site to connect, change or disconnect a network. Aglyn never sees your ShipBob or Amazon password; it keeps only the access the network grants, encrypted.\nShipMonk: connect with your API key\nShipMonk connects with an API key from your own ShipMonk account instead of a sign-in:\n1. In ShipMonk, open Account Settings, then Integration API Keys. If you have no API store yet, ShipMonk sets one up for you when you ask under Stores.\n2. Create an API key for your API store, and note the store\'s id shown beside it.\n3. On Products → Shipping & delivery, select Connect ShipMonk, paste the key, enter the store id and select Connect.\nAglyn checks the key with ShipMonk before keeping it, keeps it encrypted, and never shows it again. To use a new key, revoke the old one in ShipMonk: the card asks you to Connect again, and you paste the new one.\nAfter you connect, the card shows a webhook address and a signing secret, once. Give both to ShipMonk (its webhook settings under Integrations, or ShipMonk support) so it tells Aglyn the moment an order ships. Aglyn checks every webhook\'s signature and ignores any that does not match. Without webhooks, Aglyn still reads each order back from ShipMonk every 15 minutes. New webhook secret makes a new secret and ends the old one at once.\n- ShipBob creates a channel for Aglyn in your ShipBob account. Orders appear under it.\n- Amazon asks you to choose the marketplace whose FBA inventory ships your orders, if your seller account se'
+        text: '1. Open Products → Shipping & delivery and find the Fulfillment networks card.\n2. Next to ShipBob or Amazon Multi-Channel Fulfillment (when the card offers them), select Connect.\n3. Sign in to that account and allow Aglyn access. You come back to the store settings with the network connected.\nYou need to be an admin of the site to connect, change or disconnect a network. Aglyn never sees your ShipBob or Amazon password; it keeps only the access the network grants, encrypted.\nShipMonk: connect with your API key\nShipMonk connects with an API key from your own ShipMonk account instead of a sign-in:\n1. In ShipMonk, open Account Settings, then Integration API Keys. If you have no API store yet, ShipMonk sets one up for you when you ask under Stores.\n2. Create an API key for your API store, and note the store\'s id shown beside it.\n3. On Products → Shipping & delivery, select Connect ShipMonk, paste the key, enter the store id and select Connect.\nAglyn checks the key with ShipMonk before keeping it, keeps it encrypted, and never shows it again. To use a new key, revoke the old one in ShipMonk: the card asks you to Connect again, and you paste the new one.\nAfter you connect, the card shows a webhook address and a signing secret, once. Give both to ShipMonk (its webhook settings under Integrations, or ShipMonk support) so it tells Aglyn the moment an order ships. Aglyn checks every webhook\'s signature and ignores any that does not match. Without webhooks, Aglyn still reads each order back from ShipMonk every 15 minutes. New webhook secret makes a new secret and ends the old one at once.\nFlexport: connect with your API token\nRolling out Flexport appears on the Fulfillment networks card only once it is available on the platform you use. Until then, the card has no Flexport section'
     },
     {
         path: '/commerce-and-bookings/commerce/fulfillment-networks',
         title: 'Fulfillment networks (ShipBob, ShipMonk and Amazon MCF)',
         heading: 'Settings',
         anchor: '#settings',
-        text: '| Setting | What it does |\n| Sending | Automatic sends every paid order with a shipping address. Manual sends an order only when you select Send to it on the order. |\n| Ship option (ShipBob) | The ShipBob ship option orders ask for, as named in your ShipBob account. Standard unless you change it. |\n| Shipping service (ShipMonk) | The shipping service orders ask for. It must match a shipping mapping in your ShipMonk account. Standard unless you change it. |\n| Shipping speed (Amazon) | Standard, Expedited or Priority. Amazon bills you for the speed you choose. |\n| Marketplace (Amazon) | The marketplace whose inventory ships. |\n| Keep stock counts in step | Sets your store\'s count of each SKU to what the network can ship. Off until you turn it on. |\nPause stops new orders going to the network. Orders it already has keep coming back as they ship. An order paid while a network is paused is not sent later; send it from the order if you want the network to ship it.'
+        text: '| Setting | What it does |\n| Sending | Automatic sends every paid order with a shipping address. Manual sends an order only when you select Send to it on the order. |\n| Ship option (ShipBob) | The ShipBob ship option orders ask for, as named in your ShipBob account. Standard unless you change it. |\n| Shipping service (ShipMonk) | The shipping service orders ask for. It must match a shipping mapping in your ShipMonk account. Standard unless you change it. |\n| Ship method (Flexport) | The ship method orders ask for, such as Standard or UPS Ground. Flexport sets each order\'s delivery speed from it. Standard unless you change it. |\n| Shipping speed (Amazon) | Standard, Expedited or Priority. Amazon bills you for the speed you choose. |\n| Marketplace (Amazon) | The marketplace whose inventory ships. |\n| Keep stock counts in step | Sets your store\'s count of each SKU to what the network can ship. Off until you turn it on. |\nPause stops new orders going to the network. Orders it already has keep coming back as they ship. An order paid while a network is paused is not sent later; send it from the order if you want the network to ship it.'
     },
     {
         path: '/commerce-and-bookings/commerce/fulfillment-networks',
@@ -4559,7 +4559,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Fulfillment networks (ShipBob, ShipMonk and Amazon MCF)',
         heading: 'Shipments and tracking',
         anchor: '#shipments-and-tracking',
-        text: 'Each parcel the network ships becomes a shipment on the order, with its carrier and tracking number. When every item has shipped, the order is Fulfilled.\n- Amazon reports where each parcel is. Aglyn follows it until it is delivered or returned, for up to 30 days, and the order moves to Delivered when every parcel has arrived.\n- ShipBob tells Aglyn when a parcel is delivered or has a delivery problem, and the order shows it.\n- ShipMonk reports each package of an order, including the parts of an order it split, and where the order is. Aglyn follows it until it is delivered, for up to 30 days. If ShipMonk holds an order, for example on backorder or because it needs an address fixed, the order says so.'
+        text: 'Each parcel the network ships becomes a shipment on the order, with its carrier and tracking number. When every item has shipped, the order is Fulfilled.\n- Amazon reports where each parcel is. Aglyn follows it until it is delivered or returned, for up to 30 days, and the order moves to Delivered when every parcel has arrived.\n- ShipBob tells Aglyn when a parcel is delivered or has a delivery problem, and the order shows it.\n- ShipMonk reports each package of an order, including the parts of an order it split, and where the order is. Aglyn follows it until it is delivered, for up to 30 days. If ShipMonk holds an order, for example on backorder or because it needs an address fixed, the order says so.\n- Flexport reports each package of an order and tells Aglyn when it is delivered. If Flexport holds an order or cannot fulfill it, for example because it cannot ship to the address, the order shows Flexport\'s reason.'
     },
     {
         path: '/commerce-and-bookings/commerce/fulfillment-networks',
@@ -4575,6 +4575,111 @@ export const DOCS_SECTION_INDEX = [
         anchor: '#activity',
         text: 'Each connected network has an activity list on the card: orders sent, parcels shipped, cancellations, stock syncs and errors, newest first.\nIf a network stops accepting the connection, for example after you remove Aglyn\'s access there, the card asks you to Connect again. Orders paid in the meantime wait and are sent once you reconnect.\nDisconnect stops sending orders and removes the stored access. Orders the network already holds are left with it: check them in the network\'s own account, and ship anything it has not shipped another way.'
     },
+    {
+        path: '/commerce-and-bookings/commerce/help-desks',
+        title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
+        heading: '',
+        anchor: '',
+        text: 'Help desks: Gorgias, Re:amaze, Kustomer, Gladly and Richpanel\nRolling out Help desks appear in your console only once they are available on the platform you use. Until then, the site\'s Integrations page has no Help desks card, and contact form messages arrive in your Inbox as usual.\nConnect the help desk your support team already works in, and Aglyn keeps it up to date with your store. Each customer who has ordered from the site is added to the help desk with their recent orders, so an agent answering a ticket sees what that person bought, when, for how much and where the order stands, with a link to the order in your console.\nIf you choose, messages sent through the site\'s forms can also open as new tickets in the help desk, from the person who sent them.\nEach help desk uses your own account, connected with your own API credentials; Aglyn does not sell one and never asks for your password.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/help-desks',
+        title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
+        heading: 'Before you start',
+        anchor: '#before-you-start',
+        text: '- Role: you need to be an admin of the site to connect, change or disconnect a help desk. Editors can see the card and the sync log.\n- Verified email: verify your email address first.\n- A plan that includes your store. Help desks carry your buyers and their orders, so they come with the plans that include selling.\n- Your help desk\'s API credentials, listed for each help desk below.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/help-desks',
+        title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
+        heading: 'Connect a help desk',
+        anchor: '#connect',
+        text: '1. Open the site, then Setup → Integrations. The Help desks card lists each help desk on a row of its own.\n2. On your help desk\'s row, select Connect.\n3. Fill in the fields it asks for (see below), then select Check and connect. Aglyn checks the details with the help desk before keeping them, stores the key encrypted and never shows it again.\n4. The row shows Syncing. The first sync starts within 15 minutes.\nWhat each help desk asks for {#credentials}\n| Help desk | What to enter |\n| Gorgias | Your Gorgias domain (acme for acme.gorgias.com), and the username and API key Gorgias lists in its REST API settings. |\n| Re:amaze | Your Re:amaze brand (acme for acme.reamaze.io), the email you sign in with, and your API token from Settings → Developer → API Token in Re:amaze. |\n| Kustomer | An API key from Settings → Security → API Keys in Kustomer, with roles to read and write customers, custom objects and messages, and to read Klasses. Creating a key needs an administrator in Kustomer. |\n| Gladly | Your Gladly organization (acme for acme.gladly.com), and the email and API token of a Gladly user with the API User permission. |\n| Richpanel | Your API key from Settings → Integrations → API Keys, your store\'s app client ID from Settings → Connected Apps, and the support email address your Richpanel email channel receives mail at. |\nYou can type the domain, brand or organization as the whole address; Aglyn keeps only the first part.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/help-desks',
+        title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
+        heading: 'What your agents see',
+        anchor: '#what-agents-see',
+        text: 'Aglyn sends each person who has ordered from the site, by their email address, with their name and, when it is in international format, their phone number. People who have never ordered, such as newsletter subscribers or leads, are not sent.\nOn the first sync, Aglyn sends the site\'s paid orders from the 90 days before you connected. After that, each order is sent when it is paid, and again when it is fulfilled, delivered, refunded or canceled, so its status stays current. Test-mode orders are never sent.\nEach order carries its number, date, status, total, refunded amount, items and a link that opens it in your console.\n| Help desk | Where orders appear |\n| Gorgias | On the customer as customer data: their latest order and their 10 most recent orders. Show it in the ticket sidebar the way you show any customer data in Gorgias. |\n| Re:amaze | On the contact as customer data attributes: Last order, Last order items, Last order link and Recent orders. |\n| Kustomer | Each order as a custom object on the customer\'s timeline, updated as the order changes. Choose which custom object in Orders object (see Settings). |\n| Gladly | Each order as an activity on the customer\'s timeline, with a View order link. A new activity is added when the order\'s status changes. |\n| Richpanel | Each order in the customer\'s order history, updated as the order changes. |'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/help-desks',
+        title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
+        heading: 'Send contact form messages as tickets',
+        anchor: '#contact-form-tickets',
+        text: 'This is off until you turn it on. On the connected help desk\'s row, turn on Send contact form messages to your help desk. From then on, each message someone submits through any of the site\'s forms opens a new ticket from its sender:\n| Help desk | What a message becomes |\n| Gorgias | A new ticket from the customer. |\n| Re:amaze | A new conversation in the Channel you choose. |\n| Kustomer | A new conversation from the customer, as an inbound email message. |\n| Gladly | A task for the customer in the Inbox you choose, due a day after the message arrives. |\n| Richpanel | A new email ticket from the customer to your support email address. |\nThe ticket\'s subject is the message\'s subject answer, or the form\'s name and the sender\'s name. Its text is the message, then the form\'s other answers, then the form\'s name and the page it was sent from.\nA few things to know:\n- The sender must give an email address. A message with no email address has nobody to reply to, so it is not sent.\n- Only new messages are sent. Messages submitted before you turned this on stay in your Inbox only.\n- Your Inbox still gets every message. Sending to a help desk is in addition to the Inbox, not instead of it.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/help-desks',
+        title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
+        heading: 'Settings',
+        anchor: '#settings',
+        text: 'Each connected help desk\'s row has:\n- Channel (Re:amaze), Inbox (Gladly) or Orders object (Kustomer): where contact form messages or orders go. The menu lists what your help desk has; if it is empty, add one in your help desk, then connect again. Until you choose, the row says what it is waiting for.\n- Send buyers and their orders, on by default.\n- Send contact form messages to your help desk, off by default.\n- Pause and Resume, which stop and restart everything for this help desk. While paused, nothing new is queued for it.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/help-desks',
+        title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
+        heading: 'The sync log',
+        anchor: '#sync-log',
+        text: 'Aglyn syncs every 15 minutes. Sync now runs it at once; anything left over continues in the background. Sync log lists recent runs, what each sent, and anything the help desk refused, newest first.\nWhen something goes wrong, the row says so:\n- Connect again: the help desk no longer accepts the details you entered. Select Connect again and enter them fresh.\n- Stopped: the sync failed many times in a row. Fix what the message describes, then select Sync now.\n- An order or message the help desk refuses is tried again for a while, then listed in the sync log as Not sent, and the rest carry on.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/help-desks',
+        title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
+        heading: 'Disconnect',
+        anchor: '#disconnect',
+        text: 'Select Disconnect on the help desk\'s row and confirm. Nothing more is sent to it, and the stored key, the sync log and any orders or messages not yet sent are deleted. Customers, orders and tickets already in your help desk stay there.\nTo stop it for one site without disconnecting, turn off Help desks for that site in its plugin settings.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/help-desks',
+        title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
+        heading: 'Related',
+        anchor: '#related',
+        text: '- Orders and returns\n- Forms\n- Email platforms'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/inventory-and-erp-sync',
+        title: 'Inventory and ERP sync (Cin7 Core, inFlow, Brightpearl, Ordoro)',
+        heading: '',
+        anchor: '',
+        text: 'Inventory and ERP sync: Cin7 Core, inFlow, Brightpearl and Ordoro\nRolling out Inventory sync appears in your console only once it is available on the platform you use. Until then, no Inventory and ERP card appears on Products → Integrations, and your stock is counted the way it is today.\nIf you run your stock in Cin7 Core (formerly DEAR Inventory), inFlow Inventory, Brightpearl or Ordoro, connect that account to your store and Aglyn keeps the two in step:\n- Stock counts follow whichever side you say is right: the system\'s count of each SKU becomes your store\'s, or your store\'s count is written into the system.\n- Products can come into your store from the system, or your store\'s products can be made in the system.\n- Paid orders go to the system as sales orders, so it can pick, pack and account for them.\nA store syncs with one system at a time.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/inventory-and-erp-sync',
+        title: 'Inventory and ERP sync (Cin7 Core, inFlow, Brightpearl, Ordoro)',
+        heading: 'Connect a system',
+        anchor: '#connect-a-system',
+        text: 'You need to be an admin of the site to connect, change or disconnect a system.\n1. Open Products → Integrations and find the Inventory and ERP card.\n2. Connect the system you use:\n- Cin7 Core: in Cin7 Core, go to Integrations → API and add an API application. Paste its Account ID and Application key into the card and select Connect Cin7 Core.\n- inFlow: in inFlow, go to Options → Integrations and generate an API key (your inFlow plan needs the API access add-on). Paste the Company ID and API key and select Connect inFlow Inventory.\n- Brightpearl: enter your Brightpearl account code (the name in your Brightpearl address) and select Connect Brightpearl. Sign in to Brightpearl and allow access; you come back to Integrations with it connected.\n- Ordoro: in Ordoro, go to Account Settings → API Keys, add an API key and select Edit beside it. Paste its Client ID and Client secret and select Connect Ordoro. Ordoro\'s API is available on its Premium plan and above.\nKeys are checked with the system before they are saved, and stored encrypted. They are never shown again. Aglyn never sees your Brightpearl password.\nWhen you connect, nothing is synced until you choose what to sync below.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/inventory-and-erp-sync',
+        title: 'Inventory and ERP sync (Cin7 Core, inFlow, Brightpearl, Ordoro)',
+        heading: 'Stock counts',
+        anchor: '#stock-counts',
+        text: 'Which counts are right decides the direction:\n| Choice | What happens |\n| The system (Cin7 Core, inFlow, Brightpearl or Ordoro) | About every 30 minutes, the system\'s count of each SKU that can be sold now (on hand, less what the system has set aside for its own orders) becomes your store\'s count. Each change appears in your products\' Stock movements, counted by the system. |\n| The store | About every 30 minutes, the system\'s count of each SKU is adjusted to match your store\'s. Each run is one stock adjustment in the system; in Ordoro, each SKU\'s count is adjusted on its own. |\n| Don\'t sync counts | Counts are left alone on both sides. |\nChoose the location (in Brightpearl and Ordoro, the warehouse) whose counts are synced. To push your store\'s counts into the system you must choose one location; reading counts from the system can also add up all locations.\n- Counts are matched by SKU. A SKU only one side has is left alone, and the card says how many there were.\n- An order that is paid but not yet sent to the system is allowed for, so a unit is never sold twice while the order is on its way.\n- A product that does not track stock, or that counts stock per location, is left alone when counts come from the system.\n- Only counts that changed are written each run, and every count is written again once a day, so a count edited by hand on one side comes back in step.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/inventory-and-erp-sync',
+        title: 'Inventory and ERP sync (Cin7 Core, inFlow, Brightpearl, Ordoro)',
+        heading: 'Products',
+        anchor: '#products',
+        text: '| Choice | What happens |\n| Import from the system | About every 6 hours, products added or changed in the system are added to your store as drafts, with their SKU and price in your store\'s currency, and kept in step after that. Review a draft and publish it when it is ready. A product you delete in the store is not added again. |\n| Make store products in the system (Cin7 Core, inFlow and Ordoro) | Store products with a SKU the system does not have are made there, with their name, description and barcode, and in Cin7 Core their price and weight. In inFlow, set the price in inFlow\'s pricing scheme. In Ordoro, products are made with their name, price and barcode (as the UPC); add the description and weight in Ordoro. |\n| Match by SKU only | Nothing is made on either side. |\nBrightpearl products are made in Brightpearl, since each needs a brand, a product type and channel choices, so Brightpearl offers Import and Match by SKU only.\nEach run makes or updates up to 50 products and carries on with the rest on the next run. A product the system has no price for in your store\'s currency is not imported, and the activity says so.'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/inventory-and-erp-sync',
+        title: 'Inventory and ERP sync (Cin7 Core, inFlow, Brightpearl, Ordoro)',
+        heading: 'Orders',
+        anchor: '#orders',
+        text: 'Turn on Send paid orders and choose who orders are recorded under:\n- Cin7 Core and inFlow: the name of a customer that already exists in the system, such as "Web Sales".\n- Brightpearl: the ID of an existing Brightpearl contact.\n- Ordoro: the name of an Ordoro sales channel that already exists, such as "Web Sales". Orders are recorded under that channel, and Ordoro puts the channel\'s number in front of each order number.\nIn Cin7 Core you can also name the tax rule order lines carry; leave it empty to use the customer\'s own.\nEach paid order is sent within about 15 minutes with its items, buyer, shipping address, shipping, discount, tax and total. It carries a reference such as AG1042-3fa9c2d1 (your order number and a short code), which you can search for in the system. An order is never recorded twice: before sending, Aglyn looks for its reference in the system.\n- Items are matched by SKU. An item with no SKU is left off and the order says so. If the system has no product for a SKU, the order is not sent; add the product in the system, then select Send again.\n- If the system cannot be reached, the order is retried several times over a few hours. If it still cannot be sent, or the system refuses it, it appears under Orders not sent on the card, with the reason and Send again.\n- On the order, the system\'s section shows whether it was sent, its number in the system and its reference.\nCanceling and refunds\nWhen you cancel an order, or refund it in full:\n- Cin7 Core voids the sale, inFlow cancels the sales order, and Ordoro cancels the order. If the system will not, for example because the order has shipped, the order tells you to check it there.\n- Brightpearl: cancel the order in Brightpearl. The order reminds you, with its number there.\nAn order canceled before it was sent i'
+    },
+    {
+        path: '/commerce-and-bookings/commerce/inventory-and-erp-sync',
+        title: 'Inventory and ERP sync (Cin7 Core, inFlow, Brightpearl, Ordoro)',
+        heading: 'Activity',
+        anchor: '#activity',
+        text: 'The card lists what happened, newest first: orders sent, stock and product syncs, cancellations and errors. Sync now syncs stock and products and sends any waiting orders straight away.\nEach system limits how fast it can be called. When it asks Aglyn to slow down, everything for that store waits until the system says to come back, and then carries on where it stopped.\nIf the system stops accepting the keys or the access, the card asks you to Connect again. Orders paid in the meantime wait and are sent once you reconnect.\nPause stops all syncing until you resume. Disconnect stops syncing and deletes the stored keys and activity. Orders not yet sent stay unsent. What the system already has stays there, and so do your store\'s products and counts.'
+    },
     {
         path: '/commerce-and-bookings/commerce/order-notifications',
         title: 'Order emails & status page',
@@ -7380,7 +7485,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Forms & Lead Capture',
         heading: 'Field types',
         anchor: '#field-types',
-        text: 'A field is not one element but a few, each one you can select, move and style on its own. The picker\'s presets put them together for you; the table lists every piece, all in the element picker\'s Forms group:\n| Element | What it is | Its settings |\n| Form Control | One field\'s frame. It holds the field\'s label, its input and any help text, and ties the label to the input. | Full width?, Required? (adds an asterisk to the label) |\n| Form Label | The words that name a field, above its input. | Text |\n| Input | A box a visitor types in. | Field name, Maps to schema field, Type (Text, Email, Phone, Link or Number), Placeholder, Required?, Several lines? (a message box instead of one line), Full width?, Accessible label |\n| Helper Text | A line of guidance under a field. | Text |\n| Select | A dropdown. It holds Select Options; a visitor picks one. | Field name, Maps to schema field, Placeholder, Required?, Full width?, Accessible label |\n| Select Option | One choice in a Select. | Text, Value (what is sent; left empty, the Text is sent) |\n| Checkbox | A tick box. | Field name, Maps to schema field, Value (what a tick sends, such as Yes), Required? |\n| Radio Group | A set of Radios; a visitor picks one. | Field name, Maps to schema field, In a row? |\n| Radio | One choice in a Radio Group. | Value, Required? |\n| Choice Label | The words beside a Checkbox or Radio placed inside it. Clicking the words ticks the box. | Text |\n| Rating | Stars a visitor picks. | Field name, Maps to schema field, Stars (how many to show) |\nWhat each one sends:\n| Element | Submitted value |\n| Input | What the visitor typed |\n| Select | The chosen option\'s Value (or its Text) |\n| Radio Group | The chosen Radio\'s Value |\n| Checkbox | Its Value when ticked, nothing when not |\n| Rating | The number of st'
+        text: 'A field is not one element but a few, each one you can select, move and style on its own. The picker\'s presets put them together for you; the table lists every piece, all in the element picker\'s Forms group:\n| Element | What it is | Its settings |\n| Form Control | One field\'s frame. It holds the field\'s label, its input and any help text, and ties the label to the input. | Full width?, Required? (adds an asterisk to the label) |\n| Form Label | The words that name a field, above its input. | Text |\n| Input | A box a visitor types in. | Field name, Maps to schema field, Type (Text, Email, Phone, Link or Number), Placeholder, Required?, Several lines? (a message box instead of one line), Full width?, Accessible label |\n| Helper Text | A line of guidance under a field. | Text |\n| Select | A dropdown. It holds Select Options; a visitor picks one. | Field name, Maps to schema field, Placeholder, Required?, Full width?, Accessible label |\n| Select Option | One choice in a Select. | Text, Value (what is sent; left empty, the Text is sent) |\n| Checkbox | A tick box. | Field name, Maps to schema field, Value (what a tick sends, such as Yes), Required? |\n| Radio Group | A set of Radios; a visitor picks one. | Field name, Maps to schema field, In a row? |\n| Radio | One choice in a Radio Group. | Value, Required? |\n| Choice Label | The words beside a Checkbox or Radio placed inside it. Clicking the words ticks the box. | Text |\n| Rating | Stars a visitor picks. | Field name, Maps to schema field, Stars (how many to show) |\n| Date Picker | A date a visitor picks from a calendar, or types. | Field name, Maps to schema field, Required?, No past dates?, No future dates?, Earliest date, Latest date, Start on today?, Size, Full width?, Accessible label |\n| Time Picker | A time of day a vi'
     },
     {
         path: '/content-and-data/forms/overview',