Set up the Slabsmith connection pilot

1Open the connection card

Open Settings → Integrations and find Slabsmith connection. Review the pilot message and any existing computer's status. Download Windows setup when the verified installer link is available. Its version and SHA-256 identify the published installer; downloading it does not pair a computer or prove database access.

2Name and pair the intended computer

Enter a recognizable Computer name and choose Create pairing code. Copy code, then paste it into the Windows setup's Pair this computer field and choose Pair with SlabOS. Codes expire after 15 minutes; keep them private and create a fresh code if one expires.

An enabled Slabsmith connection prevents creating a second pairing. Repair the existing installation when appropriate. Disconnect and replacement are separate actions described below; do not disconnect a working service merely to make another code.

3Select SQL Server and the database

In Windows setup, choose a detected local SQL Server or enter the server or instance supplied by your IT contact. Choose Windows authentication or provide the SQL login and password. Find databases lists reachable user databases; select the intended Slabsmith database or its separate test copy.

Trust this SQL server's certificate changes certificate validation for this connection. Use it only when your IT contact has verified the server and requires that setting. Changing the server, database or login clears the previous database check.

4Check the selected database

Choose Check selected database. Setup verifies the expected Slabsmith table and reports its columns and database identity. A successful check uses the current login; installation separately checks the account that will actually run the Windows service. Resolve access or schema errors before continuing.

5Choose the slab image folder

Enter the SSData image folder or choose it with Choose image folder. This may be a local path or a network share. The Windows service account needs access to that location. Continue without slab images is an explicit alternative; it does not make an inaccessible image folder usable.

6Choose the Windows service account

LocalSystem is suitable when the SQL credentials and local image folder are accessible to that service. For a network share, use an existing Windows account with the required SQL and share access and Log on as a service permission. Enter its service password for a new installation. Repair preserves the installed account.

The installer stores credentials encrypted on that computer. Do not put passwords or pairing codes in a help request, screenshot or recording.

7Keep writeback off until a test copy is ready

The Windows setup includes Enable writeback to this TEST COPY of Slabsmith and Allowed write columns. Leave writeback off for ordinary read-only setup. For supervised test writes, check the separate test database, enable the test option and select only the intended discovered writable columns.

Local permission is only one requirement. SlabOS also requires the test-source designation, matching database fingerprint and approved mappings. Enabling the checkbox alone does not authorize every column or complete a write.

8Install and verify the service

Choose Install and verify service after pairing and the database check are complete. Setup checks SQL, SSData and SlabOS as the Windows service account before starting normal synchronization. Read the final result and then check the connection card for first contact.

Paired — waiting for the Windows service is different from Last sync contact. A successful install or heartbeat still needs inventory and source-mapping review. If a check fails, inspect the error and logs; do not assume the earlier desktop login proves service access.

9Review the discovered source

Open Settings → Inventory → Slabsmith read / write and choose Refresh connections & commands. Each reported source shows its name, test or read-only status and last-seen time. If no source is reported, verify the service, InventoryPilot configuration and discovery with your IT contact.

Connection name changes the displayed source name. Discovered choices expands the source's actual choice hierarchy. These values come from discovery; SlabOS does not invent missing materials, statuses or locations for a source write.

10Map fields and dimension units

Match Inventory ID, Location / rack, Status, Material, Manufacturer, Product, Color / name, Thickness, Length, Width, Barcode, Parent slab GUID and Notes to the appropriate discovered writable columns. Leave fields Not mapped when they should not be written. A source column can only be mapped once.

Set Source dimension unit to Inches or Millimeters to match the source data. Where Source status meanings appears, map each source status to the intended SlabOS inventory state or leave its existing status. Review these meanings before importing or writing availability changes.

11Confirm and save the mapping

Copy the intended test source's Discovered fingerprint into Confirm database fingerprint. Save Slabsmith mapping requires a matching fingerprint. Enable SlabOS → Slabsmith writes to this test database only for the verified test copy; Inventory ID and Location must be mapped before writes can be enabled.

Changing field mappings is blocked while source commands are queued or applying. Finish or cancel the appropriate pending work before changing a mapping. Saving a mapping does not itself update a Slabsmith stock row.

12Select fields for a linked piece

On a stock record, open Slabsmith inventory when a write-enabled test source is available. Choose the Source and check whether the piece is linked. For a linked piece, select the checkbox beside each field to change, then enter or choose its new value. Unchecked fields are not included in the request; an enabled blank field requests that value be cleared.

Use the offered source choices and their material hierarchy. Numeric dimensions use the source unit shown in the editor. Review warnings and any existing pending command before choosing Queue Slabsmith changes.

13Create a source piece from existing SlabOS stock

When the selected test source has no link for this SlabOS record, the editor offers Create piece in Slabsmith. Supply an Inventory ID and the other intended mapped values. This creates a source-side piece linked to the existing SlabOS identity; it is not a way to receive a second local inventory item.

Check for an existing source piece first. A source Inventory ID must be unique, and source database constraints may require additional values. A queued request does not prove that creation succeeded.

14Follow write history to a verified result

Use Refresh source status or Refresh connections & commands and read Write history. Queued means waiting; applying means the service has claimed the command. Applied means a source row was written and read back. Failed or conflict needs review of the result message.

If Slabsmith changed after the original read, refresh its current values and resolve the conflict before queuing a new request. Newer local edits are retained and reported when they conflict with a returned result. Verify the intended record in both systems during supervised test acceptance.

15Cancel a queued change and preserve reservations

Cancel queued change is available only while a command is queued. It cannot undo an already applied source write, and an applying command cannot be cancelled through this control.

Quote holds and job reservations remain significant. SlabOS refuses mapped source consumption or release while the piece has an active reservation. A rack move for a linked write-enabled source can queue a location update; inspect its command result as well as the local movement history.

16Repair, inspect logs or replace the computer

In Windows setup, Check / repair installed service rechecks the existing configuration and service access. Open service logs helps diagnose failures. Repair preserves the existing service account and keeps inventory history; an installation in another folder needs supervised migration.

In the web connection card, Disconnect opens a confirmation. Cancel leaves the connection intact; Disconnect computer revokes its credential while retaining inventory and source identities. Pair a replacement only as part of the planned change. Uninstall service in Windows removes the service but keeps configuration and history; use web Disconnect when access must also be revoked.

17Finish supervised acceptance

Confirm the intended computer, database identity, image access, mappings, units and first imported records. For test writes, verify create, update, conflict handling and readback against the separate test copy. Keep the pilot's pending real-installation validation distinct from successful software checks or a tutorial demonstration.