Connecting SolaStock to SolaCount makes SolaStock the inventory authority for your organization (quantities, warehouses, receipts, deliveries, counts, transfers) while SolaCount stays the accounting authority (accounts, tax, receivables, payables, currencies and the general ledger). Once connected, stock activity you post in SolaStock is sent to SolaCount automatically and posted there as journals.
This page describes the connection from the SolaStock side. SolaCount shows the same status on its own page — see Connecting SolaCount and SolaStock.
Where to find it
| Place | Path | URL |
|---|---|---|
| Connection page | Sidebar Admin → SolaCount (breadcrumb Settings → SolaCount Integration) | /inventory/integrations/solacount |
| Integration events | No menu link today — open the URL directly (the page's breadcrumb leads back to SolaCount Integration) | /inventory/integrations/solacount/events |
| Catalog synchronization | Catalog synchronization button at the top of the events page (needs Manage integration mappings & settings); see Catalog Synchronization | /inventory/integrations/solacount/catalog |
| Dashboard card | The SolaCount card on the SolaStock dashboard, with a View details link | / |
Old links keep working: /integrations/solabooks, /settings/solabooks and /integrations/solabooks/events redirect to the new addresses.
The SolaCount menu item is shown only to members who can view the integration (see Roles and permissions).
Who can connect — eligibility
| Requirement | Detail |
|---|---|
| Plans | SolaCount Premium or above and SolaStock Premium or above, both on the same organization. |
| Bundle | SolaStock Premium can also come through an eligible SolaCount bundle — SolaCount Advanced includes it. |
| SolaCount setup | SolaCount must be provisioned and its setup finished for the organization (company details, chart of accounts, tax). |
| Your access | You must be able to open both SolaStock and SolaCount in this organization. |
| Who manages it | The organization owner, or a member the owner has explicitly granted connection-management permission. Everyone else sees "Ask an organization owner or administrator to do this." |
If a plan is missing, the card names exactly which one:
- "Connecting SolaCount requires SolaCount Premium or above for this organization."
- "Connecting SolaCount requires SolaStock Premium or above for this organization. Add SolaStock Premium, or get it through an eligible SolaCount bundle (SolaCount Advanced)."
- "Connecting requires SolaCount Premium or above and SolaStock Premium or above for this organization."
The button is then Manage plans. Plans are bought in the Solavel Portal — see Subscriptions.
The SolaCount connection card
The top of the page is the SolaCount connection card. It shows the Organization, the Connected app (SolaCount), a status badge, one sentence explaining the situation and at most one action button. SolaCount's Connection Status page shows the same status, because both read it from SolaStock.
| Badge | Text you see | Button |
|---|---|---|
| Plan required | One of the plan messages above. | Manage plans |
| Finish SolaCount setup | "Finish setting up SolaCount for this organization first. The connection continues from here afterwards." | Finish SolaCount setup |
| Set up SolaCount | "SolaCount has not been provisioned for this organization yet. Open SolaCount to create its workspace securely." | none — "Nothing to do here yet. This page updates automatically once SolaCount is ready; use Refresh to check now." |
| Connecting… | "Setting up the connection — usually under a minute. This page updates by itself." (or "SolaCount is still preparing this organization.") | none. The page re-checks every 3 seconds. |
| Ready to connect | "Both apps are ready. Connecting links SolaStock to your SolaCount accounts and syncs new stock activity to SolaCount from now on. Existing records are not changed." | Connect SolaCount |
| Your input is needed | "This organization already has records in SolaCount or SolaStock. Before connecting, decide how they should be matched. Nothing changes until you confirm." / "Decisions left before you can review and connect: 3. Your progress is saved." / "All decisions are done. Review the result, then connect." | Continue setup |
| Ready to connect (everything prepared) | "Everything is prepared. Review what connecting will do, then connect." | Continue setup |
| Connected | "Stock activity syncs to SolaCount automatically." plus Last synced … or No stock activity has synced yet — new activity will sync automatically. | Open SolaCount |
| Needs attention | "Connected, but syncing needs attention. Open the details to see what is waiting." | View details |
| Paused for safety | "Syncing is paused by a safety hold. Your data is safe; an administrator can review the hold." | none |
| Connection stopped | A reason ending in Nothing was synced (see Troubleshooting). | Try again |
| Status unavailable | "We couldn't check the connection right now." | Refresh |
While an action runs, the button reads Working…. If the page cannot load at all you see Could not load the SolaCount connection with a Retry button.
View details (on Needs attention) opens a Connection details panel on the Status tab and moves you to it. It gives one plain-language reason and the number of Pending and Failed events, with a Retry button that only refreshes the status:
| Reason shown | Meaning |
|---|---|
| The connection is ready and syncing can continue. | Everything is fine; the card will update. |
| The connection is configured, but its delivery worker is unavailable. An administrator needs to check the running service. | The service that delivers events is not running. Events wait safely. |
| Some deliveries need review. Check their status before attempting the original action again. | Open the events page. |
| Some setup requirements remain incomplete. Review the required setup steps. | Finish the setup tasks. |
| Current application access needs review by an administrator. | Someone lost access to SolaStock or SolaCount. |
| The connection needs review before syncing can continue. | Generic. |
Below it: "Refresh the status after the issue is resolved. Do not disconnect or repeat financial actions to clear this warning." Manage plans opens the Solavel Portal in a new tab so this page stays where it is.
If a button points to a SolaCount step you cannot open (for example Finish SolaCount setup as a non-owner), you see: "Only an organization owner can open this step in SolaCount. Ask the owner to finish Finance setup or manage the plan, then refresh."
Connect (fresh organization)
Use this when the badge says Ready to connect — typically a new organization where neither app has business records that need matching.
- Open Admin → SolaCount.
- Read the card. It confirms both apps are ready and that existing records are not changed.
- Click Connect SolaCount (bottom of the card). The button shows Working… and the badge switches to Connecting….
- Wait — usually under a minute. Do not click again; the page refreshes itself.
- When the badge shows Connected, you are done. Open SolaCount takes you to SolaCount.
What the automatic connection does:
- Links the default-chart accounts. SolaStock is linked to the SolaCount accounts it posts to (inventory, goods received not invoiced, cost of goods sold, adjustment gain/loss and the others listed in What flows to SolaCount). On a standard SolaCount chart of accounts these are validated and linked automatically; the status then shows Account mappings: Automatic.
- Maps the standard units and categories automatically. Both apps ship the same standard units (each, kg, box…) and categories. They are matched by standard name and symbol (units) or name path (categories), never overwriting anything. The setup summary shows "Units and categories ready — 37 units and 18 categories matched automatically" (your numbers may differ). Only custom or conflicting records are shown for a decision.
- Syncs new stock activity from the connection date. It creates no opening balances or transactions for customers and suppliers, and does not change existing records.
If the organization turns out to have records that need matching, the card switches to Your input is needed and the guided setup opens below it.
Continue setup (organization with existing records)
If either app already has items, stock quantities, units, categories, customers or suppliers that need matching, a guided setup opens on the same page. You reach it with Continue setup on the card here, or from SolaCount's Continue setup, which signs you in to SolaStock and opens the exact unfinished step (/integrations/solacount?task=<step>). You never start over.
The header shows Step X of Y with a progress bar, and All steps lets you jump back to a step you already finished. Steps with nothing to do are skipped.
| Step | What you do |
|---|---|
| Preparation | SolaCount supplies the financial settings automatically: organization identity, the SolaCount workspace, base currency ("Base currency inherited from Finance: AED"), accounts and taxes ("14 account candidates and 3 taxes were checked from SolaCount."). Successful checks stay compact. |
| Business records | A summary table lists Items, Units and categories, Customers, Suppliers, Warehouses and Currencies with Total, Ready automatically and Needs your decision. Open a section and choose an action for each record that needs one (see the table below). Long lists have Search this list and paging. |
| Physical count | For items where the apps disagree, keep a value or enter the counted quantity ("Keep this value or enter the physical count"), then click Confirm quantities and continue. |
| Review Finance accounts | Choose the SolaCount accounts used by inventory workflows ("Saving a selection does not approve or activate the connection."). Each row says where it stands: Saved selection, Proposed for review, Ambiguous — select an account, Missing account, Missing default — review proposal, Account code conflict — review required, Invalid — review required or Optional — not required for current operations. A changed selection must be saved before you continue: "Save your account changes before continuing." If your organization requires a separate reviewer, this step is done by that person (see Separate review). |
| Start date | Review existing documents around the connection start date (Confirm review) and choose the date from which stock activity syncs. SolaStock fills in a suggested date and time from your device and tells you so: "This is a suggested date and time from your device. Review or change it, then Continue to save it. It has not been saved yet." Continue saves it and prepares the review ("The connection is ready for review."); no financial entries are created. An invalid date shows "Choose a valid start date and time to continue."; unreviewed documents show "Review the listed documents before continuing." |
| Result preview | Read What connecting will do, give the explicit approval, then connect. |
Customers and suppliers are always shown in Business records, even when they already match, so you confirm each one. A customer and supplier that are the same business appear as one row to confirm. Actions offered per record type:
| Record | Actions you can choose |
|---|---|
| Item with an exact SKU/barcode match | Confirm the match, reject it, require a physical count, or keep it blocked. Exact matches can be confirmed together with Select displayed exact matches. |
| Item only in SolaCount | Create the SolaStock item, keep it as a SolaCount service (no stock), exclude it from this connection, require a physical count, or keep it blocked. |
| Item only in SolaStock | Keep SolaStock as authority, exclude it, require a physical count, or keep it blocked. |
| Unit | Select a SolaStock unit, define a unit conversion, or keep it blocked. |
| Category | Select a category, propose creating it, or keep it blocked. |
| Customer / supplier | Match to an existing SolaCount contact, propose creating it in SolaCount, or Review this record later. |
| Warehouse, tax, currency | Select the matching record (or keep/exclude a currency). |
Every answer is saved in a private setup draft: "This answer is saved to the setup draft only and does not change operational records." Nothing changes in either app until the final step. You can leave at any time and resume later.
Result preview and connect
The preview lists What connecting will do:
- Link N business records between SolaStock and SolaCount as reviewed.
- Sync new stock activity to SolaCount from <start date>.
- Create no opening balances or transactions for customers and suppliers; existing records are not changed.
If something is still open you see The preview is not ready yet with a numbered list, for example "Complete the required physical counts.", "Review the cutoff documents.", "Resolve the inventory-value difference." or "Owner approval and accounting review confirmation are still required." Return to required tasks returns to the first open step.
When all checks pass you see Setup preview is ready. Tick the explicit approval, then click Connect to SolaCount and confirm in the dialog. On success: "The organization-scoped connection is active." Both apps then show Connected.
If a record changed in SolaCount or SolaStock while you were reviewing, the page shows Records changed since this review: "SolaCount or SolaStock records have changed. Refresh the review and confirm the updated choices and start date before connecting. Existing business records are preserved." Click Refresh review; the dialog warns "Restart this connection review with the latest records? The previous start date and approvals will be cleared. No business records or financial transactions will be changed." A decision that cannot be saved shows its error beside the exact record it concerns, so you can fix that row.
Separate review
Some organizations require a different person to approve the accounting setup (segregation of duties). The card then says "Your organization requires a separate reviewer to approve the accounting setup before connecting." and the setup shows Accounting review is the next step — "Your owner decisions are saved. 2 Finance accounts still require an authorized connection reviewer." The reviewer opens Admin → SolaCount, completes Review Finance accounts and clicks Confirm accounting review. The owner cannot do this step themselves under that policy.
After connecting — the Status tab
Once connected, the page has two tabs below the card: Status and Connection wizard (the reviewed setup, kept for reference).
Status shows a Connection status list:
| Row | Meaning |
|---|---|
| Inventory authority after activation | SolaStock |
| Accounting authority | SolaCount |
| Activation | Active, or Safely paused |
| Delivery | Enabled / Disabled |
| Accounting mappings | Configured automatically when accounts were linked from the default chart |
While setup is still in progress the same card also shows Setup status, Current step and Decisions remaining.
Owners and connection managers also see a collapsible Technical details section: Dedicated worker (Running / Disabled), Finance receiver (Yes / No), Last sync, Last successful authoritative stock read, Pending events, Failed events and Ignored.
The page refreshes its status every 15 seconds (every 3 seconds while connecting) and whenever you return to the tab.
What flows to SolaCount
When you post a stock document, SolaStock records an integration event and delivers it to SolaCount, which posts a journal to the linked accounts. Delivery is authenticated and retried safely; SolaStock never writes directly into SolaCount's data.
| Event type (as shown) | Created when |
|---|---|
| Internal consumption issued / Internal consumption returned | An Internal Consumption issue or return is posted |
| Purchase order approved | A purchase order is approved (no journal) |
| Opening stock posted / Opening stock reversed | Opening stock is posted or reversed |
| Adjustment posted / Adjustment reversed | A stock adjustment is posted or reversed |
| Goods receipt posted / Goods receipt reversed | A goods receipt (GRN) is posted or reversed (including receipts made from a Receiving Request) |
| Supplier return posted / Supplier return reversed | A Supplier Return is posted, or exactly reversed |
| Landed cost posted / Landed cost reversed | A Landed Cost is posted or reversed |
| Transfer posted | A transfer between warehouses is posted |
| Stock count posted | A stock count is posted |
| Sales order confirmed, Stock reserved, Stock reservation released | Sales order and reservation steps |
| Pick list completed, Package packed, Shipment posted | Fulfilment steps; the shipment moves stock out |
| Sales return posted / Sales return reversed | A sales return brings stock back, or is reversed |
| Historical FIFO cost corrected | A correction of the FIFO cost of earlier shipments is posted (it adjusts cost of goods sold and Inventory) |
Accounts used:
| Account role | Used for |
|---|---|
| Inventory | Value of stock on hand |
| Goods received, not invoiced (GRNI) | Stock received before the supplier bill |
| Cost of goods sold | Cost of stock delivered |
| Inventory adjustment gain / loss | Count and adjustment differences |
| Opening balance offset | Opening stock |
| Internal consumption expense | The expense charged when materials are issued internally; chosen per line, item, category or as the connection default |
| Supplier return clearing | Goods sent back to the supplier until the supplier credit is posted |
| Transfer clearing, Landed cost clearing, Purchase price variance | Transfers in transit, freight/duty (the account you choose in Landed Costs), rounding |
Worked example 1: goods receipt and shipment
Al Noor Trading LLC receives 100 boxes of "A4 Paper Box" into Dubai Main at AED 12.00 each. When the goods receipt is posted, SolaStock creates a Goods receipt posted event; SolaCount posts:
| Account | Debit (AED) | Credit (AED) |
|---|---|---|
| Inventory | 1,200.00 | |
| Goods received, not invoiced | 1,200.00 |
Later, 40 boxes are shipped to a customer. The Shipment posted event leads SolaCount to post Dr Cost of goods sold AED 480.00, Cr Inventory AED 480.00. The supplier bill for AED 1,200.00 + 5% VAT is entered in SolaCount and linked to the receipt, which clears the GRNI.
Worked example 2: an event blocked by mapping
Sara Khan posts goods receipt GRN-00131 for a new item, USB-C Hub 7-in-1, created in SolaStock after the connection. The dashboard SolaCount card turns to Needs attention.
- Omar Haddad (SolaStock Administrator) opens
/inventory/integrations/solacount/events, searchesGRN-00131. - The row shows Goods receipt posted, status Blocked by mapping, mapping Incomplete. View shows Attempts 1 and the reason in Last error.
- He completes the missing mapping on the connection page (Continue setup / the item's mapping), then returns, opens the event and clicks Retry → "Retry attempted."
- The status moves to Sent; SolaCount posts Dr Inventory AED 2,400.00 / Cr Goods received, not invoiced AED 2,400.00. The card returns to Connected.
Integration events page
Open it at /integrations/solacount/events (breadcrumb SolaCount Integration → Events). The page title is SolaCount Integration Events.
Filters (top toolbar): status (All statuses), event type (All event types), a search box "Search event, document, or failure", and from / to dates.
The list shows the latest 100 matching events.
Columns: Occurred, Event, Document (links to the source document), Status, Mapping (Complete or Incomplete), and a View button.
Catalog synchronization (top, for people who manage mappings) opens Catalog Synchronization.
Every event type SolaStock records has a readable name in the Event column and its own entry in the event-type filter (All event types), in English and Arabic: Opening stock posted, Opening stock reversed, Adjustment posted, Adjustment reversed, Goods receipt posted, Goods receipt reversed, Purchase order approved, Supplier return posted, Supplier return reversed, Landed cost posted, Landed cost reversed, Transfer posted, Stock count posted, Internal consumption issued, Internal consumption returned, Sales order confirmed, Stock reserved, Stock reservation released, Pick list completed, Package packed, Shipment posted, Sales return posted, Sales return reversed and Historical FIFO cost corrected. To find the events of one document, pick its type in the filter or type the document number in Search.
If there are none: No events — "Events appear when inventory documents post (with an active tenant)."
Event statuses
| Status | Meaning |
|---|---|
| Pending | Created, waiting to be processed. |
| Review required | Held until someone reviews it (for example history before the start date). |
| Blocked by mapping | An item, account or other record is not mapped yet. Fix the mapping, then retry. |
| Blocked by contract | Held by a currency or other contract rule. |
| Ready | Ready to be delivered. |
| Processing | Being delivered now. |
| Retry scheduled | Delivery failed temporarily; it will be retried automatically. |
| Sent | SolaCount accepted it. |
| Failed | Delivery failed; see Last error. |
| Dead letter | Stopped after repeated failures; needs a person to review. |
| Ignored | Deliberately not sent. |
| Superseded / Reversed | Replaced by a later event, or reversed. |
Typical lifecycle: Pending → Ready → Processing → Sent; on a temporary error → Retry scheduled → Processing; after repeated failures → Dead letter.
Review, retry or ignore an event
- Click View on the row. A dialog shows the event type and status, Event UUID, Document, Mapping, Attempts, Failure category, Last error, Lease expiry and the Payload.
- Choose an action at the bottom:
- Retry — delivers the event to SolaCount again. Notice: "Retry attempted." Retrying is safe; SolaCount never posts the same event twice.
- Ignore (only for Pending or Failed) — stops the event from being sent. Notice: "Event ignored."
- For a Dead letter: enter a Review note (required), then Mark reviewed ("Dead letter marked reviewed.") or Review and retry.
- Close returns to the list.
If the mapping is Incomplete, fix the mapping first — retrying an event that is still blocked by mapping will block again.
The action buttons are hidden while delivery is paused. The page then shows Integration delivery paused — "SolaCount delivery is temporarily paused for currency-contract maintenance. Existing events are preserved."
Documents that start in SolaCount
The flow above goes from SolaStock to SolaCount. Four things also travel the other way, each handled by its own SolaStock page. The warehouse never needs accounting permissions for them; every request is signed and checked against your current access.
| SolaCount document | Arrives in SolaStock as | Who acts in SolaStock |
|---|---|---|
| A supplier bill sent to the warehouse | A Receiving Request (RR-n) |
A purchasing approver approves and picks the warehouse; warehouse staff receive goods against it. |
| A sales invoice sent to the warehouse | A Fulfillment Request (FR-n) |
A sales approver approves the warehouse; staff reserve, pick, pack and ship its sales order. |
| A cash sale (receipt) | A Cash Sale Dispatch request (only where the cash hand-over is enabled) | Staff confirm what physically left the warehouse. |
| Products, units and categories | Catalog records, in the other direction too: SolaStock items are sent to SolaCount (Catalog Synchronization) | Administrators resolve stuck records. |
What comes back to SolaCount is the physical truth: the goods receipt, the shipment, the supplier return, the sales return. The accountant keeps the commercial truth (the bill, the invoice, credits, refunds, payments). The two never overwrite each other, which is why a receipt reversal that touches a posted bill is held for the accountant (see Receiving Requests).
Related behaviour:
- Customers and suppliers synchronize continuously. A document that needs a customer or supplier that is not yet linked waits instead of failing: "The connection for Gulf Aqua Supplies LLC is not ready. Retry shortly. If it remains blocked, ask the organization integration manager to review its Finance link. The document remains a draft." Ambiguous or conflicting links are never guessed: "This organization has conflicting integration links. Ask its integration manager to review the connection before posting." Supplier identities that could be two different records go to an explicit owner review.
- Notifications. Warehouse staff get warehouse notifications; integration administrators are also notified when a party or catalog sync needs a person.
- One organization never delays another. Delivery failures are isolated per organization and stage, so a problem in one connection does not hold up deliveries for the rest.
Valuation in the base currency
When SolaStock is connected, stock is valued in one currency: the base currency of your SolaCount organization (for example AED). A goods receipt in another currency (a USD purchase order, for example) is converted at SolaCount's exchange rate for the receipt date, and that base cost is what enters stock. If SolaCount has no valid rate for the date you get "No valid Finance exchange rate is available for USD on 2026-10-11. Add the rate in Finance or select a receipt date with a valid rate."; a currency that is not enabled for the organization shows "The document currency is missing or is not enabled for this organization." Reversals and adjustments of documents that were born while you were not connected stay in the currency they were valued in.
If an organization that was connected is disconnected, SolaStock keeps its reviewed valuation protected. Posting more stock then shows "Reconnect the existing Finance connection before posting stock. Its reviewed inventory valuation remains protected." Reconnect through this page before posting.
Posted adjustment and journal values do not depend on which warehouses the viewer is assigned to: the value of a posted document is always calculated from the whole document, so an accountant with a narrow warehouse scope still sees the same journal amounts as an administrator.
Historical workflows and opening stock from SolaCount
In a connected organization SolaStock owns stock, so SolaCount does not record stock itself. Instead, SolaCount's SolaStock group (in its Inventory panel) runs SolaStock's own workflows on your behalf through a signed workspace channel:
- Opening stock — recorded in SolaStock (SolaCount says "Record opening stock in SolaStock."). The signed workspace exposes SolaStock's native opening stock, including reviewed opening valuations, and posts them as Opening stock posted events.
- Historical documents — suppliers, customers, purchase orders, sales orders, goods receipts, shipments and sales returns can be listed, created and posted through the same channel. They keep SolaStock's own permissions, dates, stock checks and event lifecycle; a historical goods receipt keeps its original reference number instead of getting a new one.
Every request is signed and checked against your current Solavel access, so a member who could not do the action in SolaStock cannot do it from SolaCount either. The resulting documents appear in SolaStock like any other and create integration events in the normal way.
Roles and permissions
| Who | Can |
|---|---|
| Organization owner with access to both apps | View, connect, run the guided setup, approve and activate, retry/ignore events. |
| Member granted connection management by the owner | The same as the owner for this connection. There is no self-elevation. |
| Connection reviewer (separate review policy) | Complete Review Finance accounts and Confirm accounting review. |
| SolaStock Administrator | Everything in SolaStock, including viewing the integration and retrying/ignoring events. Connecting additionally requires SolaCount access and connection-management permission. |
| Inventory Manager | View the connection page and events (read-only). |
| Warehouse Manager, Warehouse Operator, Inventory Viewer | No access to the SolaCount menu. |
Permissions by key
| Permission | Key | Owner / Administrator | Org-wide Inventory Manager (Manager/Member) | Accountant | Scoped roles |
|---|---|---|---|---|---|
| View SolaCount integration status & events | inventory.integration.view |
Yes | Yes | Yes | No |
| Prepare reviewed SolaCount connection decisions | inventory.integration.setup |
Yes | No | No | No |
| Manage and approve an organization connection | inventory.integration.connection_manage |
Owner (or explicitly granted) | No | No | No |
| Manage integration mappings & settings | inventory.integration.manage |
Yes | No | No | No |
| Review connection accounting-role decisions | inventory.integration.accounting_review |
Yes | No | Yes | No |
| Retry / ignore integration events | inventory.integration.retry |
Yes | No | No | No |
| Export integration events | inventory.integration.export_events |
Yes | No | No | No |
On the events page, Retry, Ignore, Mark reviewed and Review and retry appear only with Retry / ignore integration events and only while delivery is not paused. Viewing stays available even if the plan changes, so an existing connection never becomes an unexplained error.
App roles are assigned in the Portal — see Application roles and Team.
Access messages in the setup:
- "SolaCount access is required for this organization. Ask the organization owner to enable access, then return to this wizard."
- "SolaStock access is required for this organization."
- "Connection-management permission is required. Ask the organization owner; self-elevation is not available."
- "This organization requires a different authorized reviewer under its segregation-of-duties policy."
- "Connection authority could not be verified safely. Try again or contact support."
Troubleshooting
| Message | Cause and fix |
|---|---|
| Setup stopped because SolaCount has not issued the connection keys yet. Nothing was synced. Try again in a moment. | Temporary. Click Try again after a minute. |
| Setup stopped because new connections are temporarily turned off. Nothing was synced. Try again later. | Platform maintenance. Try later. |
| Another setup attempt is already running. Try again in a moment. | Someone (or another tab) already clicked connect. Wait for the badge to change. |
| Setup stopped because SolaCount's chart of accounts is missing an account SolaStock posts to. Nothing was synced. Check the chart of accounts in SolaCount, then try again. | An inventory account was deleted or archived in SolaCount. Restore it, then Try again. |
| Setup stopped before it finished. Nothing was synced. You can safely try again. | Click Try again. A setup stuck on Connecting… is also reported this way. |
| Ask an organization owner or administrator to do this. | You are not allowed to manage the connection. Ask the owner. |
| Sync is awaiting a healthy delivery worker. An administrator can review transport status. (dashboard card) | Delivery is temporarily not running. Events wait safely and are sent once it recovers. |
| Integration delivery paused | A safety hold is active. Events are kept and sent after the hold is lifted. |
| Event shows Blocked by mapping | Open the connection, complete the missing mapping, then Retry the event. |
| "Enable internal consumption in the reviewed SolaCount connection workflows before posting." | This connection's reviewed workflow list does not include internal consumption. Connections made from now on include it; for an older connection ask an integration administrator (or Solavel support) to add it. |
| "Set up landed costs: choose the clearing account." | No landed cost clearing account yet. See Landed Costs. |
| "Supplier-return integration is not ready. Ask an integration administrator to review the receiving, return-clearing account and Finance consumer setup." | A supplier return is blocked until the return-clearing account and SolaCount's side are ready. See Supplier Returns. |
| "Reconnect the existing Finance connection before posting stock." | The organization was disconnected after being connected. Reconnect on this page. |
| Retry/Ignore buttons missing | You lack Retry / ignore integration events, or delivery is paused. Ask the owner or wait for the hold to lift. |
| "Review and retry" shows the notice Retry | That is the normal confirmation for this action. Check the status column. |
Tips:
- Retrying is always safe. Every stopped state says Nothing was synced, and retried events are never posted twice.
- You only connect once. Afterwards the card stays Connected and changes only if syncing needs attention.
- Use the event Search with a document number (for example GRN-00042) to find what happened to a specific document.
Related
- Connecting SolaCount and SolaStock (SolaCount side)
- Opening stock
- Internal Consumption, Landed Costs, Supplier Returns, Catalog Synchronization
- Receiving Requests, Fulfillment Requests, Cash Sale Dispatch, Warehouse notifications
- Purchasing, Sales fulfillment, Adjustments, Transfers
- Settings
- Application roles, Subscriptions