Owner command line pilot

Operate selected SleekSync workflows from a terminal during an approved private API pilot.

  • Home
  • / Owner command line pilot

Controlled pilot ยท Approval required

Work with SleekSync from your terminal

Try setting up a shop from your terminal: configure a store, define products and prices, work with customers and appointments, and inspect rental quotes, tickets, and recorded payments. The local demo lets you try these commands without an account or live shop data. Live shop commands use your SleekSync sign-in, MFA, and assigned tenant and store permissions after pilot approval.

New owners can request a guided trial from the terminal before they have an account. SleekSync reviews the request and arranges a walkthrough before provisioning access.

Requires Node 24. The synthetic demo needs no account or deployed pilot and prints fresh appointment and report dates when it starts. Live integration and shop commands need an enabled deployment; integration commands also require an expiring scoped key. The CLI has no third-party dependencies. Download the single script and demo helper into the same folder, then run the command below. At the shop> prompt, type help for topics or help tickets for exact ticket commands. Try stores list, then type exit when finished.

# PowerShell, from the folder containing both downloaded scripts
node .\sleeksync.mjs demo --interactive
# At shop> type: help
# Then try: stores list
# When finished, type: exit

To use the sleeksync commands below from any folder, download the package archive and install it with Node's package manager. If you keep the two scripts instead, run each command as node .\sleeksync.mjs from their folder.

# PowerShell, from the folder containing the downloaded archive
npm install --global .\sleeksync-owner-cli-0.68.2.tgz
sleeksync help
Synthetic local preview

See the CLI run a shop session

This short recording shows selected moments from the actual CLI running against a local fixture. It starts with a synthetic trial receipt, then shows store setup, catalog creation, a fixture stocktake, customer creation, a rental quote, ticket booking, fixture cash checkout, return, an appointment, and ecommerce order shipping and delivery. The downloadable demo and transcript include the full sequence, payment and report reads, and safe request replays. The fixture advances its clock to the displayed pickup date. No live lead, tenant, payment, or garment changes. Live booking, checkout, and return grants remain disabled during review. Run node .\sleeksync.mjs demo from the folder containing both scripts to replay it, or add --interactive to enter the printed shop commands yourself in order.

Read the full local walkthrough transcript

What the pilot can do

Start with a guided trial request

Send your business contact and meeting availability from the terminal, then keep the request ID while SleekSync reviews it. An account is created only after approval.

Check your shop access

Run a read-only access diagnostic, then use one in-memory MFA session for several staff commands in the same tenant and store.

Check before you promise

Read published products, rental policy, and current or date-scoped garment availability from your terminal.

Update guarded inventory

Set an approved SKU's aggregate level using the count you just read and a stable idempotency key. Conflicts require review.

Manage contacts and fitting measurements

Find assigned stores, create and correct customer contact and profile details, inspect measurement history, and record or correct a retail customer's fitting with your own sign-in and store permissions.

Manage physical stock

As tenant owner, define a store category and shared SKU, then find garments by SKU or barcode, add one from a same-store item or visible SKU, and correct its size, condition, or notes.

Run a physical stock count

Snapshot an assigned store, record present or missing garments, review conflicts and variances, then approve and post with the current revision and exact session confirmation.

Price an exact item

As a tenant owner, read and set one store-specific physical item's direct rental and purchase prices with MFA, price permission, and a current-value check.

Set category tax

As a tenant owner, read and set a store category's tax components from your own percentages, with MFA, a current-value check, and an audit record.

Create an assigned store

As the tenant owner and staff administrator, create a store from a profile file. The transaction checks your plan limit and assigns the store to your account; a retained request key makes retries safe.

Create a staff login

As the tenant staff administrator, use MFA and a retained request ID to provision a login at selected stores. The CLI asks privately for the new password and PIN.

Manage basic CLI bookings

As owner, set store contact details, a named timezone, weekly hours, and appointment capacity; then read the schedule, preview available starts, book an unassigned appointment, and reschedule or cancel that CLI booking before staff or Google Calendar is attached.

Prepare, ship, and confirm ecommerce delivery

List paid processing, shipped, or delivered orders in an assigned store; inspect items and the private address; prepare exact reserved items; then record shipment and confirmed delivery after the reviewed migrations and event workers are enabled.

Track order integration progress

Inspect preparation, shipment, and delivery event queue states, retry attempts, and failure codes from the terminal without exposing the private order snapshot. Confirm separately that recipients applied sent updates.

Inspect tickets

Find tickets by stored status, reservation date, or expected-return date and inspect item status using your staff view permission.

Quote a simple rental

Request a temporary server-priced quote for one direct-price physical rental. The quote makes no stock hold and booking remains disabled during review.

Quote a physical purchase

Request a temporary server-priced retail quote for one direct-price garment. The staged USD cash sale remains disabled during review.

Preview checkout state

Review a ticket's stored amount, customer IDs, assigned items, pickup state, and payment count. This read-only view does not collect money or release stock.

Preview a rental return

Inspect the item, expected date, and reviewed snapshot for a CLI-booked, cash checked-out single-garment rental. The return write remains disabled during review.

Review ticket and payment activity

Summarize stored ticket balances and group ticket-linked payment activity by processor, currency, status, and type for one store and time window. These are not settled revenue figures.

Inspect recorded payments

Read a ticket's recorded tender, amount, and status with staff permission. Provider settlement still requires separate reconciliation.

Send an inquiry

Submit a structured customer request for staff follow-up. This does not hold stock or create a payment.

Can I run the whole shop this way?

Not yet. The download includes staged exact-item rental creation, cancellation, a direct-price USD cash sale, cash checkout, and healthy rental return commands, but staff access remains disabled until release checks pass. Rental quotes are limited to direct-price items with configured tax, without customer discounts or rule-based deposits. Purchase quotes are limited to one direct-price retail garment. Rental and purchase quotes require current operator evidence that the store checks out in USD; they do not hold stock. Customer consent, discounts, and other profile edits, changes to assigned or synced appointments and general cancellation, ticket creation and fulfillment, holds, payment collection, and provider reconciliation are not available. Exact ecommerce item preparation, tracked shipping, and delivery confirmation are included in the download but await reviewed database migrations and protected workers before they can run in a hosted shop. Shipping records an existing carrier tracking number; it does not buy a label or email the customer. Delivery records an operator confirmation and does not verify a carrier scan. CLI bookings do not assign staff or sync Google Calendar. Account sign-in, authenticator setup, access requests, and key management can be done from the terminal once the pilot deployment is enabled. SleekSync still reviews each request and designates an API administrator.

Get started

  1. Install Node 24. Download both scripts and run node .\sleeksync.mjs demo --interactive from their folder, or install the package archive as shown above and run sleeksync demo --interactive. Both use a synthetic local session. Run sleeksync access config, or node .\sleeksync.mjs access config with the scripts, to check public settings without signing in. Live commands load those settings from the SleekSync POS app. For an approved custom or local deployment, set SLEEKSYNC_APP_URL to its origin.
  2. If you do not have an account, save the example below as trial-request.json with your contact and meeting details. Run sleeksync trial request --file trial-request.json. This uses the website's guided intake and returns a request ID. SleekSync arranges a walkthrough and reviews the request before provisioning an account.
  3. Check your authenticator status from the terminal. Enroll one there if needed, then find your tenant and send an access request. SleekSync must review and enable it.
  4. Once approved, the designated API administrator creates an expiring key in the terminal. Use the assigned API URL and key to run the connection check.

Keep the request file private. The CLI shows its receipt without printing contact fields. A phone number is optional; preferred plans are basic, grow, or advanced. A request does not create an account.

{
  "first_name": "Ada",
  "last_name": "Owner",
  "email": "[email protected]",
  "business_name": "Ada Formalwear",
  "meeting_availability": "Tuesday after 10 AM Eastern",
  "preferred_plan_key": "basic",
  "store_count": "1"
}

If the app's configuration route is unavailable, the CLI checks its public JavaScript for one matching project and anon key. If both automatic paths fail, ask SleekSync for this deployment's public Supabase URL and anon/publishable key. Set both in your shell before an access or shop command. Never use a service-role or secret key. An approved tenant and deployed management function are still required.

# Only if automatic discovery fails and SleekSync gives you public settings
$env:SLEEKSYNC_SUPABASE_URL = 'https://YOUR_PROJECT.supabase.co'
$publicKey = Read-Host 'Public anon/publishable key' -AsSecureString
$env:SLEEKSYNC_SUPABASE_ANON_KEY = [System.Net.NetworkCredential]::new('', $publicKey).Password
sleeksync access tenants --email [email protected]

access mfa-status prompts for your password and reports only your verified authenticator count; it does not confirm shop access. Other signed-in access commands prompt for your password and six-digit authenticator code without saving a session. Enrollment shows a private otpauth:// URI; keep it out of recordings and logs. Create access-request.json with your actual workflow:

{
  "system_name": "Owner CLI",
  "workflow_summary": "Read catalog and availability; submit inquiries.",
  "direction": "read",
  "inventory_source_of_truth": "sleeksync"
}
# PowerShell: public project settings load from the SleekSync POS app
sleeksync access mfa-status --email [email protected] # password prompt; no authenticator code
sleeksync access enroll --email [email protected] # once, if needed
sleeksync access tenants --email [email protected]
sleeksync access request --email [email protected] --tenant YOUR_TENANT_UUID --file access-request.json
sleeksync access status --email [email protected] --tenant YOUR_TENANT_UUID
# After approval, the designated API administrator creates a scoped key:
sleeksync access create --email [email protected] --tenant YOUR_TENANT_UUID --name 'Owner terminal' --scopes catalog:read,inventory:read --expires 90

Key creation shows the secret once. Keep it out of command arguments, shell history, screenshots, and recordings. In PowerShell, prompt for it in your current session:

# PowerShell, after SleekSync enables your tenant
$env:SLEEKSYNC_API_BASE_URL = 'https://YOUR_PROJECT.supabase.co/functions/v1/api-v1'
$secret = Read-Host 'SleekSync API key' -AsSecureString
$env:SLEEKSYNC_API_KEY = [System.Net.NetworkCredential]::new('', $secret).Password
sleeksync status

Replace the example base URL with the exact one assigned to your tenant. Close the shell or clear its environment when finished.

Rotate an expiring API key

Create a second key before the old one expires. Save its secret when shown, switch your integration to it, and verify the connection and other uses of the old key. Then look up the old key ID and revoke it. A failed check leaves the old key available for recovery. Key management asks for a fresh password and authenticator code each time. Staff shop commands do not use this integration key.

# Approved API administrator: create a replacement with the needed scopes
sleeksync access create --email [email protected] --tenant YOUR_TENANT_UUID --name 'Owner terminal replacement' --scopes catalog:read,inventory:read --expires 90
# Save its one-time secret in your approved secret manager.
# Switch SLEEKSYNC_API_KEY to the replacement, then check every integration.
sleeksync status
sleeksync access status --email [email protected] --tenant YOUR_TENANT_UUID
sleeksync access revoke --email [email protected] --tenant YOUR_TENANT_UUID --id OLD_KEY_UUID

Try the pilot commands

Find your assigned store ID in the first command, then run the read-only diagnostic. It checks access, the columns used by basic customer, inventory, ticket, and appointment reads, and whether an operator has reviewed this store's USD quote currency, but does not prove that staged writes or complete workflows are ready. Replace store 12, SKU DR-100, and every uppercase date or timestamp token with values from your approved test shop. Use future YYYY-MM-DD dates for rental availability and quotes; appointment timestamps must include an offset matching the store's saved timezone on that date. Use an actual bounded window for reports and lists: return dates use YYYY-MM-DD, while timestamps use RFC3339 with an explicit offset. Add --json for structured results. The date check is a snapshot; it does not reserve stock. Physical item status is also a snapshot, not date-scoped rental availability.

sleeksync shop stores list --email [email protected] --tenant YOUR_TENANT_UUID
sleeksync shop doctor --email [email protected] --tenant YOUR_TENANT_UUID --store 12
sleeksync shop stores timezone get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --json
sleeksync shop stores timezone set --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --file store-timezone.json
sleeksync shop stores hours get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --json
sleeksync shop stores hours set --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --file store-hours.json
sleeksync shop stores capacity get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --json
sleeksync shop stores capacity set --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --file store-capacity.json
sleeksync shop stores profile get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --json
sleeksync shop stores profile set --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --file store-profile.json
sleeksync shop stores create --email [email protected] --tenant YOUR_TENANT_UUID --file new-store.json
sleeksync shop categories list --email [email protected] --tenant YOUR_TENANT_UUID --store 12
sleeksync shop categories create --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --file new-category.json
sleeksync shop tax-rates get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --category 5 --json
sleeksync shop tax-rates set --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --category 5 --file category-tax.json
sleeksync rental policy --store 12
sleeksync catalog list --store 12 --limit 20
sleeksync shop skus create --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --file new-sku.json
sleeksync shop skus list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --sku SUIT-NEW
sleeksync shop inventory items --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --sku DR-100
sleeksync shop counts options --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --json
sleeksync shop counts list --email [email protected] --tenant YOUR_TENANT_UUID --store 12
sleeksync shop counts get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --session COUNT_UUID --json
sleeksync shop inventory get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 101 --json
sleeksync shop inventory add --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --file inventory-item.json
sleeksync shop prices get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 101 --json
sleeksync shop prices set --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 101 --file item-price.json
sleeksync shop inventory update --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 101 --file inventory-update.json
sleeksync shop inventory sync --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 101 --confirm-item 101
sleeksync shop customers list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --name Ada
sleeksync shop customers list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --customer-email [email protected]
sleeksync shop customers list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --phone '555-0100'
sleeksync shop customers list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 42
sleeksync shop customers export --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --output .\customer-contacts.json
sleeksync shop customers get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 42 --json
sleeksync shop customers measurement-fields --email [email protected] --tenant YOUR_TENANT_UUID --store 12
sleeksync shop customers measurements --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 42
sleeksync shop customers measurements create --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 42 --file measurement.json
sleeksync shop customers measurements update --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 42 --measurement 135 --file measurement-correction.json
sleeksync shop customers create --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --file customer.json
sleeksync shop customers update --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 42 --file customer-update.json
sleeksync shop tickets list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --limit 20
sleeksync shop orders list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --limit 20
sleeksync shop orders get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id ORDER_UUID --json
sleeksync shop orders prepare --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id ORDER_UUID --items ITEM_UUID --idempotency-key NEW_REQUEST_UUID --confirm-order ORDER_UUID
sleeksync shop orders get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id ORDER_UUID --show-shipping yes
sleeksync shop orders ship --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id ORDER_UUID --carrier ups --tracking 1Z999AA101 --idempotency-key NEW_SHIPMENT_UUID --confirm-order ORDER_UUID
sleeksync shop orders list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --status shipped
sleeksync shop orders deliver --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id ORDER_UUID --idempotency-key NEW_DELIVERY_UUID --confirm-order ORDER_UUID --confirm-delivery yes
sleeksync shop orders list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --status delivered
sleeksync shop orders events --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id ORDER_UUID --json
sleeksync shop tickets list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --status "Checked Out"
sleeksync shop tickets list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --date-field return --date-start RETURN_START_DATE --date-end RETURN_END_DATE
sleeksync shop tickets get --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 92
sleeksync shop tickets quote --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --customer 27 --item 101 --pickup FUTURE_PICKUP_DATE --return LATER_RETURN_DATE
sleeksync shop tickets sale-quote --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --customer 27 --item 109
sleeksync shop tickets checkout-preview --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 92
sleeksync shop tickets return-preview --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --id 92
sleeksync shop payments list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --ticket 92
sleeksync shop reports ticket-balances --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --from 'WINDOW_START_RFC3339' --before 'WINDOW_END_RFC3339'
sleeksync shop reports payment-activity --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --from 'WINDOW_START_RFC3339' --before 'WINDOW_END_RFC3339'
sleeksync shop appointments list --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --from 'WINDOW_START_RFC3339' --before 'WINDOW_END_RFC3339'
sleeksync shop appointments check --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --at 'FUTURE_LOCAL_START_RFC3339' --duration 60
sleeksync shop appointments capacity-window --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --from 'FUTURE_WINDOW_START_RFC3339' --before 'FUTURE_WINDOW_END_RFC3339' --duration 60 --step 30
sleeksync shop appointments create --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --customer 27 --at 'FUTURE_LOCAL_START_RFC3339' --idempotency-key shop12-booking-0001
sleeksync shop appointments reschedule --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --booking-key shop12-booking-0001 --from 'FUTURE_LOCAL_START_RFC3339' --at 'NEW_LOCAL_START_RFC3339'
sleeksync shop appointments cancel --email [email protected] --tenant YOUR_TENANT_UUID --store 12 --booking-key shop12-booking-0001
sleeksync inventory availability --store 12 --sku DR-100
sleeksync inventory availability --store 12 --sku DR-100 --pickup FUTURE_PICKUP_DATE --return LATER_RETURN_DATE
sleeksync inventory availability --store 12 --sku DR-100 --json

For several staff commands, sign in once with the in-memory shop session. It discovers your assigned shops and stores, then asks you to choose if there is more than one. Enter shop command names at its prompt; the chosen email, tenant, and store stay fixed until you exit. The token is discarded when the process closes. Integration API commands still run separately with your approved scoped key.

sleeksync shop session --email [email protected]
shop> help
shop> help tickets
shop> doctor
shop> stores timezone get --json
shop> stores timezone set --file store-timezone.json
shop> stores hours get --json
shop> stores hours set --file store-hours.json
shop> stores capacity get --json
shop> stores capacity set --file store-capacity.json
shop> stores profile get --json
shop> stores profile set --file store-profile.json
shop> stores create --file new-store.json
shop> stores list
shop> categories list
shop> categories create --file new-category.json
shop> tax-rates get --category 5 --json
shop> tax-rates set --category 5 --file category-tax.json
shop> skus create --file new-sku.json
shop> skus list --sku SUIT-NEW
shop> inventory add --file inventory-sku-item.json
shop> prices get --id 103 --json
shop> prices set --id 103 --file item-price.json
shop> inventory items --sku DR-100
shop> counts options
shop> counts list
shop> customers list --name Ada
shop> exit

A tenant owner can read the store timezone with shop stores timezone get --json. Save the example below as store-timezone.json and run shop stores timezone set --file store-timezone.json. Choose the store's actual IANA location. For an edit, copy the returned timezone into expected; the database records changed values in a private audit entry.

{
  "expected": null,
  "desired": "America/New_York"
}

Then inspect weekly hours with shop stores hours get --json. Save the example below as store-hours.json and run shop stores hours set --file store-hours.json. For an edit, copy the complete returned hours into expected. The database checks the prior values and records changed hours with a private audit entry. CLI booking writes require both settings and the database checks their local offset, opening hours, and capacity. Existing POS appointment behavior is unchanged. Review staff availability before booking.

{
  "expected": null,
  "desired": {
    "sunday": { "enabled": false, "start": "09:00", "end": "17:00" },
    "monday": { "enabled": true, "start": "09:00", "end": "17:00" },
    "tuesday": { "enabled": true, "start": "09:00", "end": "17:00" },
    "wednesday": { "enabled": true, "start": "09:00", "end": "17:00" },
    "thursday": { "enabled": true, "start": "09:00", "end": "17:00" },
    "friday": { "enabled": true, "start": "09:00", "end": "17:00" },
    "saturday": { "enabled": true, "start": "09:00", "end": "11:00" }
  }
}

Read the store's current appointment limit with shop stores capacity get --json. Save the example below as store-capacity.json, using that returned limit as expected, then run shop stores capacity set --file store-capacity.json. The owner needs MFA and store view and edit permission. Changed CLI limits have a private audit record. Review existing bookings before lowering the limit; they are not moved automatically.

{
  "expected": 1,
  "desired": 2
}

Read the store name and contact details with shop stores profile get --json. Save the example below as store-profile.json, replacing all six expected fields with the returned profile. Provide all six desired fields, using null to clear an optional one. Then run shop stores profile set --file store-profile.jsonand reread the profile. Owner MFA and store view or edit permission apply. A changed CLI edit has a private audit record, and a stale comparison is rejected.

{
  "expected": { "store_name": "Downtown", "store_address": null, "store_city": null, "store_state": null, "phone": null, "email": null },
  "desired": { "store_name": "Downtown Studio", "store_address": "12 Main Street", "store_city": "Boston", "store_state": "MA", "phone": "555-0100", "email": "[email protected]" }
}

To open a second store, save the example below as new-store.json and run shop stores create --file new-store.json. Keep its UUID request key for an exact retry. The tenant owner must also be the staff administrator. The store plan limit applies, and a successful creation assigns the store to that owner. List stores again, then open a new shop session for the new store. This command does not create a tenant or staff account.

{
  "request_key": "77777777-7777-4777-8777-777777777777",
  "profile": { "store_name": "North Studio", "store_address": "12 Main Street", "store_city": "Boston", "store_state": "MA", "phone": "555-0100", "email": "[email protected]" }
}

A tenant staff administrator can also create a staff login. Save the example below as new-staff.json, then run sleeksync shop staff create --email [email protected] --tenant YOUR_TENANT_UUID --file new-staff.jsonoutside the in-memory shop session. The CLI asks for administrator MFA, then privately prompts for the new password and four-digit PIN. Keep the request file and use the same details and secrets on an uncertain retry. The deployed provisioning function checks the administrator, assigned stores, and plan limit; no password or PIN belongs in the JSON file. After creation, run sleeksync shop staff list --email [email protected] --tenant YOUR_TENANT_UUID --json to review active staff IDs, login emails, roles, and assigned stores. The directory requires administrator MFA and supports --limit and --after for more accounts. To remove a login, use sleeksync shop staff remove --email [email protected] --tenant YOUR_TENANT_UUID --id STAFF_ID --confirm-email STAFF_EMAIL outside the shop session. It checks the active directory first, then uses the existing retryable staff removal job. Removal permanently deletes the login; an uncertain result needs account review, and a retry requires an existing job for that staff ID. The current administrator can transfer that authority with sleeksync shop staff transfer-admin --email [email protected] --tenant YOUR_TENANT_UUID --file transfer-admin.json. The file holds one request UUID plus the replacement's ID and email. Keep it for an exact retry if the response is uncertain; the retry checks the original receipt because the former administrator loses staff-management authority as soon as the transfer succeeds.

{
  "request_id": "55555555-5555-4555-8555-555555555555",
  "email": "[email protected]",
  "first_name": "New",
  "last_name": "Employee",
  "user_role": "employee",
  "user_phone": null,
  "store_ids": [12]
}

A tenant owner can list visible categories and their store assignments. To create one for this store, save the example below as new-category.json. Choose storefront visibility explicitly; false keeps it private while you prepare its SKU, stock, and price. The account needs category view or create permission. Set the category tax rate separately before quoting.

{
  "category_name": "Formalwear",
  "description": "Suits and jackets",
  "ecommerce_visible": false
}

Read the current rate with shop tax-rates get --category 5 --json. Save the example below as category-tax.json, then run shop tax-rates set --category 5 --file category-tax.json. For an edit, copy the complete returned rate object into expected. Enter the four percentages from your shop's tax policy; SleekSync sums them and audits a changed rate. The command needs tenant ownership, MFA, and store tax permission. A rate does not certify the store currency or enable staged bookings and sales.

{
  "expected": null,
  "desired": {
    "state_tax_rate": "6.00",
    "county_tax_rate": "1.25",
    "federal_tax_rate": "0.00",
    "others_tax_rate": "0.50"
  }
}

A tenant owner can define a new shared SKU from a private new-sku.json file. The account needs create permission for the selected store, and the row policy checks ownership again. Replace the example category ID with one returned by the directory. The CLI checks that it is visible and assigned to this store or global. Inspect the exact SKU after a duplicate or uncertain response; creation never overwrites an existing definition. It creates no physical item or price. Read and set its direct item price after adding physical stock.

{
  "sku": "SUIT-NEW",
  "product_name": "Classic suit",
  "brand_name": "Example",
  "category_id": 5,
  "color": "Navy"
}

To add a physical garment, choose a source item already in the selected store and save this example as inventory-item.json. For the first item of an existing SKU in this store, find its exact code with shop skus list --sku SUIT-NEW, then save the SKU example below as inventory-sku-item.json. The account needs inventory view and create permission. The new item receives its own ID and barcode. The SKU must be visible to the signed-in account; this command does not create a new SKU or configure prices. Keep the same retry key after an uncertain response and check the item directory first.

{
  "source_item_id": 101,
  "size_range": "44R",
  "garment_condition": "Excellent",
  "notes": "Synthetic stock receipt",
  "idempotency_key": "inventory-demo-0001"
}
{
  "sku": "SUIT-NEW",
  "size_range": "44R",
  "garment_condition": "Excellent",
  "notes": "Synthetic stock receipt",
  "idempotency_key": "inventory-sku-0001"
}

Use the item ID returned by the add command; for example, read item 103 with shop prices get --id 103 --json. Save the example below as a private item-price.json file, then run shop prices set --id 103 --file item-price.json. For a later change, copy the returned price ID and both current amounts into expected. The command needs MFA and price view plus create or edit permission and tenant ownership. It refuses a direct price when an applicable SKU or size price takes priority. A successful change queues a product update; delivery and quote eligibility need separate checks.

{
  "expected": {
    "price_id": null,
    "retail_rental_price": null,
    "retail_purchase_price": null
  },
  "desired": {
    "retail_rental_price": "50.00",
    "retail_purchase_price": "80.00"
  }
}

Use shop inventory get --json to read an item before correcting its size, condition, or notes. Copy all three current values into expected and put the fields to change in changes. Save this example as inventory-update.json. The account needs inventory view and edit permission. A stale edit fails without overwriting the POS record. New item additions and corrections queue product events with the database change. A queued result means delivery will retry; keep notes and JSON output private.

{
  "expected": {
    "size_range": "40R",
    "garment_condition": "Good",
    "notes": "Synthetic stock receipt"
  },
  "changes": { "size_range": "44R", "garment_condition": "Excellent" }
}

If a saved item did not reach a storefront, inspect webhook delivery logs and the retry queue first. After the queue is clear, shop inventory sync requires inventory view and edit permission plus a matching --confirm-item. It resends the item's current state to every matching active product webhook. A recipient may see a duplicate event. The queue and this manual action send current product state, not the original snapshot.

To count a store from the terminal, read shop counts optionsfor visible category IDs and the approval threshold. Save the first example as count-create.json; omit category IDs to count the full store. Creation snapshots inventory and active ticket state. If its response is uncertain, list existing counts before creating another. Read the count with --json to inspect every item, then save batches from the second example as observations.json. A quantity of 1 means present, 0 means absent, and null clears an observation. Keep notes and full count output private.

{"name":"October stocktake","category_ids":[4,5]}
{"observations":[{"item_id":101,"observed_quantity":1},{"item_id":102,"observed_quantity":0,"note":"Shelf and back room checked"}],"reason":"First pass"}

Use the latest returned revision for each step. Review how to treat unscanned items, resolve conflicts or new items with counts refresh and a recount, and obtain approval if the variance exceeds the store threshold. Posting requires the exact session UUID twice. The database repeats revision and stock checks under locks and records movements. For an uncertain post response, read the count before trying again. With the count outbox migration installed, each posted movement queues a storefront product update in the same transaction. Run shop counts events for the posted session to see each movement's queue status. A sent event still needs storefront verification. Older installations can post without this event; use the separate shop inventory sync command only after confirming no event is queued or retrying. Live count posting still needs a real owner and tenant workflow test.

shop> counts options --json
shop> counts create --file count-create.json
shop> counts get --session COUNT_UUID --json
shop> counts save --session COUNT_UUID --revision 1 --file observations.json
shop> counts review --session COUNT_UUID --revision 2 --unscanned review
shop> counts get --session COUNT_UUID --json
shop> counts approve --session COUNT_UUID --revision N --reason 'Verified variance'
shop> counts post --session COUNT_UUID --revision N --reason 'Verified shelf count' --confirm-session COUNT_UUID
shop> counts events --session COUNT_UUID

Search the assigned store's customers by part of a name or by exact ID, stored email, or stored phone number. Email capitalization and phone formatting must match the saved contact. Keep customer output out of shared terminal logs and recordings.

shop customers export --output .\customer-contacts.json collects the assigned store's contact directory into a UTF-8 JSON file without replacing an existing path. It includes IDs, names, phone numbers, and email addresses, but not addresses, notes, or measurements. Check the command's exit code and keep that file private. Use --json instead to print the contacts to stdout. The result is marked consistent_snapshot: false because records can change while pages are read; it is not a database backup.

For customer creation, save this synthetic example as customer.jsonand replace its details for the approved shop. Address and preference notes are optional. The account needs customer view and create permission for the assigned store.

{
  "name": "Demo Customer",
  "email": "[email protected]",
  "address": "12 Example Street",
  "special_preferences_notes": "Synthetic fitting preference",
  "idempotency_key": "demo-customer-0001"
}

For a contact or profile update, save this example as customer-update.json. Read the current record with shop customers get --json. Set expected to those contact values and the exact current address or notes being changed, using null when missing. The account needs customer view and edit permission.

{
  "expected": { "name": "Demo Customer", "phone": null, "email": "[email protected]", "address": "12 Example Street", "special_preferences_notes": "Synthetic fitting preference" },
  "changes": { "email": "[email protected]", "special_preferences_notes": "Updated synthetic preference" }
}

For a retail customer's fitting, first list the configured measurement field names. Save values using those exact names in a private measurement.json file. The account needs customer view and create permission. Keep the retry key if the response is lost; read the history and retry only with the same file and key.

{
  "measurements": { "Chest": 40, "Waist": 32 },
  "notes": "Synthetic fitting record",
  "idempotency_key": "measure-demo-0001"
}

To correct that record, read measurement history with --jsonand copy its timestamp, values, and notes into the expectedsection of measurement-correction.json. Supply the complete new field set and notes. The account needs measurement view and edit permission. A concurrent change stops the correction; reread history before preparing a new file. Keep fitting details out of shared logs.

{
  "expected": {
    "last_modified_at": "2026-09-30T12:00:00.123456",
    "measurements": { "Chest": 40, "Waist": 32 },
    "notes": "Synthetic fitting record"
  },
  "measurements": { "Chest": 41, "Waist": 32 },
  "notes": "Corrected synthetic fitting record"
}

Staff commands prompt for your password and authenticator code. The SKU directory uses staff view permission and shows visible tenant definitions, including those without physical stock for a tenant owner. It does not show prices. Use --sku for an exact code or --offset to page through the list. Physical item lookup uses inventory view permission and supports exact SKU or barcode filters and --after paging. The capacity check is a preview for a new appointment and does not reserve a time. The capacity window checks stored weekly hours and several candidate starts; an explicit offset must match the saved store timezone. Staff and calendar availability are not checked, and booking rechecks local hours and capacity. Customer contacts, measurements, and appointment times are limited to an assigned store; keep that output out of shared recordings. Existing measurement records still need POS for deletion. Keep the customer file private. If creation times out, retry with the same file and idempotency key. New keys retain a fingerprint of the original request, so later profile edits do not invalidate an exact retry. Older keys may still conflict after a profile edit. A conflict can also mean a changed request, duplicate email or phone, or a key retained after deletion; inspect the directory before changing the request. A saved customer with a queued integration event must not be created again. Delivery may retry with the same event ID; inspect webhook deliveries before manual recovery. If an update reports a conflict, reread the customer before editing again. A queued update event retries with the same event ID; do not repeat the contact edit to trigger a sync. Contact updates do not change measurements or consent. Rental and purchase quotes are valid for five minutes and require POS, inventory, and customer permission. They make no reservation; their price and availability are rechecked at booking or sale. The staged purchase sale requires confirmed USD cash, creates its ticket and pickup in one transaction, and remains disabled for staff pending release checks. The order inbox requires E-commerce Orders or Prepare Orders view permission and shows paid processing, shipped, or delivered ecommerce orders and item preparation state in an assigned store, without customer contact details or payment amounts. The prepare command requires edit permission, exact reserved item IDs, and a retained UUID for safe retries. Use shop orders get --show-shipping yes with E-commerce Orders view permission to inspect the private address, then shop orders ship with edit permission, all items prepared, and a real carrier tracking number. After confirming actual delivery, use shop orders deliver with a new UUID and explicit confirmation. shop orders events shows scoped queue states without private snapshots; a sent state still needs recipient verification. Shipping does not buy a label, send customer email, or collect payment. Delivery does not verify a carrier scan. The order migrations and event workers have not been enabled on hosted staging. Ticket commands require view permission and show stored fulfillment status, not a confirmed payment settlement. Use the displayed ticket ID to inspect items, filter by an exact stored --status, and use --before or --after for older ticket or item pages. Ticket date filters use an inclusive start and exclusive end, with a maximum 31-day window. An expected-return date alone does not prove that the return is still outstanding. The ticket balance snapshot also requires Reports permission. It summarizes stored amounts and does not verify provider settlement or accounting revenue. The payment activity report groups ticket-linked recorded transactions by processor, currency, status, and type for a bounded store/time window; unlinked and older unrecorded payments are absent. Recorded payment inspection requires Reports and ticket view permission for the store. It omits card fields and provider metadata, and its status is not proof of settlement. Checkout and return previews require POS and Inventory edit permission and Reports view permission. They show point-in-time snapshots and do not collect payment, release a garment, or record a return. The staged return supports only an early or on-time healthy garment from a one-item CLI rental paid in cash; damaged, missing, late, fee, and refund cases remain in POS. Staff return execution is disabled pending target and live tenant checks. Appointment windows and booking times require timestamps with timezone offsets. A booking needs an existing customer ID and a stable idempotency key; retry only with the same key and details. To move an unassigned CLI booking, provide its original time and key. The new time must pass the store hours and capacity checks. Reschedule or cancel before staff or a Google event is attached. Booking does not assign staff or sync Google Calendar. Inventory writes require an expected current quantity and a stable idempotency key. If the level changed, read it again and reconcile before trying a new change. Use sleeksync help for all command forms.

Tell us what you need to do without opening the POS

Share the customer, rental, inventory, reporting, or payment workflow you want to run from a command line. We will confirm what is available in your tenant and what needs to be built.

Request a CLI pilot review