Manage subscription
The billing portal is not available yet. When it launches, sign in using a link sent to your purchase email. Under the planned subscription terms, upgrades and downgrades take effect on your next billing date.
Support
Help for your FactoryGrids setup.
Check your Mac requirements, get started, and work through common connection issues. Need a hand? Send us the details of your setup and what happened.
Before you install
Start with a compatible Mac.
FactoryGrids requires macOS 27 or later on Apple Silicon. Check both before downloading or troubleshooting a launch issue.
Minimum macOS 27
Check About This Mac
Open the Apple menu in the top-left corner of your screen and choose About This Mac. Check the macOS version and the chip.
The chip must be Apple Silicon, such as an Apple M-series chip. An Intel Mac does not meet the requirement.
- Operating system
- macOS 27 or later.
- Mac hardware
- A Mac with Apple Silicon.
- Local connections
- Server Mode and Mac to Mac sync run on your own local network, with optional NAS storage.
- Internet
- Sales-channel sync needs an internet connection. Your working data is stored on your Mac or configured NAS; connected services exchange the data needed for their features.
Getting started
Build up your setup, one step at a time.
Start with the Mac app, then add your machines and services. Connect one device or integration first so you can check the setup before expanding it.
Check your Mac
Confirm macOS 27 or later and an Apple Silicon chip in About This Mac.
Download the app
Go to the downloads page for the signed and notarized Mac release and each platform's availability.
Install and launch
Open the .dmg, double-click the .pkg inside, and follow the installer. Choose FactoryGrids for the Mac app, then launch it from Applications. The Free plan needs no license key.
Connect your setup
Check the integrations directory for your machine or service and its Live or Beta status, then follow the connection guides below.
Review your first priorities. Once your data is current, open Dashboard to review stock risk, days of cover, and top movers. Use these signals to decide which products or production runs need attention.
Every plan includes basic local backup, restore, and complete data export. Keep a separate backup before making major changes to your storage or setup.
Connection guides
Connect your first machine or channel.
Choose a guide for the details to gather, the fields to use, and a first connection check. Start with one connection and confirm its data before expanding your setup.
Have access to the device or service account you manage. Check your plan's included connections and the directory's Live and Beta statuses. Keep keys, passwords, and tokens in the app, out of support messages.
Bambu Lab
Have ready: the printer's local IP address, serial number, and access code, with the printer and Mac on the same reachable network.
- Check Bambu Lab's instructions for your model and firmware. FactoryGrids' direct local connection needs access to the printer's local services; firmware with authorization controls may require Developer Mode. Review Bambu Lab's security guidance before enabling it.
- In FactoryGrids, open Manufacturing > Printers > Add Bambu Printer. Enter a display name, IP Address, Serial, and Access Code. Leave Use Bambu Cloud off for this local setup.
- Choose Test Connection, then Add Printer. Confirm that the machine's status appears before sending work.
If it fails: recheck the current IP and access code, local-network access, and your firmware's connection restrictions. Include the model, firmware, and exact error when requesting help.
Official guidance: Bambu Lab third-party connection and Developer Mode guidance.
Klipper and Moonraker
Have ready: a working Klipper installation with Moonraker, the host address and port, and its API key if authentication is required.
- Confirm that the printer works through its existing interface, such as Mainsail or Fluidd. Find the Moonraker service's address and port; its default HTTP port is 7125.
- Open Manufacturing > Printers > Add Moonraker. Enter a display name, Host, and Port, or try Discover. Match Use HTTPS to your actual server configuration.
- If the server requires a key, enable Require API key and enter the key provided by your Moonraker administrator. Choose Test Connection, save the connection, and check the printer's status.
If it fails: confirm you used Moonraker's port, which may differ from the web interface's port. For an authorization error, check the key and server access rules with your administrator instead of disabling authentication.
Official guidance: Moonraker server configuration and authentication.
OctoPrint
Have ready: an OctoPrint server that already connects to your printer, its host and port, and an API key for an authorized OctoPrint user.
- Sign in to OctoPrint and confirm the printer is connected. Obtain an application key for your user from OctoPrint's key settings; ask its administrator if you cannot manage keys.
- Open Manufacturing > Printers > Add OctoPrint. Enter a display name, Host, Port, and API Key. Match Use HTTPS to the server.
- Choose Test Connection and save. Confirm live status first. The OctoPrint user behind the key also needs permission for any later file upload or print action.
If it fails: open the same server in your Mac's browser, then check the address, key, and user permissions. A connected server and a connected printer are separate checks.
Official guidance: OctoPrint application keys.
Amazon
Have ready: an authorized Selling Partner API application, its Login with Amazon client ID and client secret, and a refresh token for the seller account you intend to connect.
- If you own a private SP-API application, follow Amazon's self-authorization process for your seller account. The account's primary user must authorize it. New developer access or application approval is handled by Amazon.
- In FactoryGrids' Integrations, select Amazon > Configure. Choose the correct Marketplace, then enter LWA Client ID, LWA Client Secret, and Refresh Token.
- Choose Save, then Test. Confirm the returned marketplaces match your account. Review the first imported data before enabling Automatic Sync.
If it fails: check that all three credentials belong to the same authorized application and account, and that its roles allow the requested data. A Seller Central password is not a refresh token.
Official guidance: Amazon private application authorization.
Etsy
Have ready: access to your Etsy shop, its numeric shop ID, and an approved Etsy developer application. Etsy requires both application credentials and shop authorization for private shop data.
- In FactoryGrids' Integrations > Etsy, locate Keystring (Client ID) and Shop ID. These identify the developer application and shop; they are not your Etsy password.
- For a new connection, request setup help to confirm the supported sign-in route for your FactoryGrids version before authorizing the shop. Provider callback and credential requirements must match that route.
- After authorization is confirmed and the required fields are populated, choose Save and Test. Check that the returned shop is yours before importing listings or orders.
If it fails: keep the exact sign-in or token error and your app version. A rejected callback or missing application credential needs a supported connection flow; repeatedly pasting tokens will not fix it.
Official guidance: Etsy application credentials and shop authorization.
Shopify
Have ready: your store's myshopify.com domain and an Admin API access token authorized for that store, with the read access needed for products, inventory, and orders.
- Ask the store owner or app administrator to confirm the token's permissions and expiry. New apps use Shopify's current developer setup; an older custom-app tutorial may not match your account.
- In FactoryGrids' Integrations > Shopify, enter Shop Domain and Admin API Access Token. Use the store domain, not an admin-page URL, a storefront token, or your account password.
- Choose Save, then Test. Confirm the returned store name and compare initial orders and stock with Shopify.
If it fails: check token expiry, app installation, and read permissions. Before relying on an expiring token for ongoing sync, confirm a supported renewal setup for your FactoryGrids version.
Official guidance: Shopify access tokens and renewal.
Provider documentation checked 8 October 2026. Device firmware, account permissions, and app versions can change the available connection steps. A successful connection check does not establish support for every model or operation.
Billing and activation
Get help with paid access.
Paid activation and trial enrollment are not available yet. The billing portal is not available yet.
License delivery and recovery
When paid access launches, you will receive a separate license key to enter in the Mac app. Activate it online before using the supported offline mode. Key delivery and recovery are separate from your billing receipt and portal. Paid activation and trial enrollment are not available yet.
For billing, key-delivery, or recovery help, check our contact section for current availability. Keep license keys and other private credentials out of your message.
Troubleshooting
Check the basics first.
These checks help narrow down launch, network, and integration issues. Keep the exact error message so you can include it in your support request.
Confirm that your Mac runs macOS 27 or later and uses Apple Silicon. Open the .dmg and run the .pkg installer, choosing FactoryGrids, then launch it from Applications. If macOS displays a warning or the app closes unexpectedly, record the exact message and when it happens. Contact support with those details.
Check that the Mac and the device are powered on and connected to the intended local network. A guest network, VPN, or network isolation setting can prevent local devices from reaching each other. Confirm the machine model and connection method against the integrations directory. For a managed network, ask your network administrator to check local connectivity.
Check that the host Mac is running and reachable on your local network. If you use NAS storage, confirm that the storage is available from your Mac and that your account still has access. Before changing storage locations or permissions, keep a separate backup. If the connection still fails, include which Macs are affected and whether the issue involves local or NAS storage in your support request.
Confirm your internet connection and that you can sign in to the service directly. Check the integration's Live or Beta status in the directory, and confirm that the connected account still has the required access. Record the service name, the last successful sync if known, and the error message. Keep passwords, access tokens, and API keys out of your support request.
Before acting on a stock or production signal, check when your sales channels last synced and compare the inventory shown with your current records. Confirm which machines and services are connected. If a figure still looks wrong, note the view name, app version, and relevant date range for your support request. Keep customer details and credentials out of your message.
Basic local backup, restore, and complete data export are included with every plan. Keep a separate copy of your backup and confirm which data you intend to restore before making changes. If you are unsure about a recovery step, contact support with a description of the issue and the backups you have available.
Contact support
Tell us what happened.
Check our contact section for current availability. Have your app and Mac versions, the steps that reproduce the issue, and the exact error ready so we can understand what happened.
Your app and Mac
FactoryGrids version, macOS version, and Apple Silicon chip. Include which companion device or host Mac is involved, if relevant.
Steps and results
What you were trying to do, the steps you took, what you expected, and what happened instead. Tell us whether it happens every time.
Connection details
The machine model or integration name, and whether the issue involves a local connection, sales-channel sync, or NAS storage.
Error or screenshot
Include the exact error text in your message. Have a screenshot ready if useful, with customer information, passwords, API keys, and other private details redacted.