FS-DOC-01Operations
Launch Plan
Multichannel Inventory Sync
[YourCompany.com] · Fulfilment Department · Prepared by FullSpec · [Today's Date]
This Launch Plan is your single reference for everything that happens between now and go-live for the Multichannel Inventory Sync automation. It covers what is being built, how the four build stages work, what FullSpec needs from you to get started, what your role looks like once the automation is running, and how to recognise that it is working as intended. FullSpec handles all technical configuration, integration work, and testing end to end. Your role is to provide tool access, confirm one configuration decision before build begins, and review exception flags once the system is live.
01What you're launching
Right now, every order, return, or purchase order receipt across your sales channels triggers a chain of manual updates. A fulfilment coordinator logs into Shopify, Amazon Seller Central, and Linnworks separately, records figures in a master spreadsheet, recalculates stock per SKU, and re-enters those numbers into each platform one by one. This takes around nine hours every week and the timing gaps between updates cause oversells, missed reorder triggers, and end-of-week finance reconciliation that is always fighting stale data. The automation being built will replace all eleven of those manual steps with a real-time sync that fires the moment a stock-changing event is detected on any connected channel, pushing accurate quantities everywhere within seconds and alerting your buying team and finance system automatically.
Process
Multichannel Inventory Sync
Trigger
An order is placed, a return is confirmed, or a purchase order is marked received on any connected channel
Final output
All channels updated with correct stock quantities, audit row written to Google Sheets, low-stock Slack alert fired if threshold is reached, and inventory journal posted to Xero
Agents being built
2 agents: Stock Level Sync Agent and Reorder Alert and Finance Sync Agent
Tools involved
Shopify, Amazon Seller Central, Linnworks, Xero, Slack, Google Sheets
Volume
Approximately 320 stock update events per month across all channels
Launch PlanPage 1 of 4
FS-DOC-01Operations
02How the build works
The build runs across four sequential stages: Connect, Build, Test, and Launch. FullSpec manages every technical task at each stage. Your involvement is focused and time-limited, mostly front-loaded into the Connect stage where tool access is confirmed. The Standard build is rated moderate complexity and carries an estimated delivery window of four to five weeks from the close of Connect.
Complexity level: Moderate. Estimated delivery window: 4 to 5 weeks. The delivery clock starts at the close of Connect, not payment. Build cannot begin until all credentials listed in Section 03 are confirmed and the configuration decision in that section is resolved.
1Connect
Business days 1 to 3
FullSpec
Sends credential request list, audits your Linnworks configuration to confirm it is set as the stock source of truth, documents reorder thresholds per SKU, and identifies any Amazon API rate-limit constraints.
You
Provide API credentials and access for all six tools (see Section 03), confirm Linnworks is the authoritative stock record, and confirm or supply reorder threshold data per SKU.
2Build
Business days 4 to 16
FullSpec
Configures trigger listeners on Shopify, Amazon Seller Central, and Linnworks. Builds the Stock Level Sync Agent including quantity calculation logic, anomaly flagging, and API push calls to each channel. Then builds the Reorder Alert and Finance Sync Agent including threshold comparison logic, Slack alert formatting, and Xero journal entry posting. Writes the audit log to Google Sheets.
You
Available to answer clarifying questions about SKU structure or threshold rules. No technical input required during this stage.
3Test
Business days 17 to 20
FullSpec
Runs end-to-end tests using sample orders, returns, and purchase receipts on staging channels. Validates quantities across all platforms, confirms Xero journal entries, checks Slack alert formatting, and verifies anomaly flagging for negative-quantity scenarios. All issues are resolved before live credentials are touched.
You
Reviews a test summary shared by FullSpec and confirms the outputs match your expected quantities and Slack message format. Sign-off required before proceeding to Launch.
4Launch
Business days 21 to 25
FullSpec
Cuts over to live channel credentials, monitors the first 48 hours of real runs, reviews the Google Sheets audit log for unexpected results, and delivers the SOP and runbook to your fulfilment team.
You
Notifies your fulfilment coordinator and warehouse manager that the automation is live. Reviews the first anomaly flag (if any) to confirm the human review step is understood.
Launch PlanPage 2 of 4
FS-DOC-01Operations
03What FullSpec needs from you
FullSpec only needs access to your existing tools. No technical knowledge is required from you or your team. The table below lists every credential needed and when to have it ready. Having all items confirmed before Connect closes keeps the delivery window on track.
Shopify
Admin API access token with read and write permissions on Inventory and Orders
Before Connect closes
Amazon Seller Central
SP-API credentials: Client ID, Client Secret, Refresh Token, and Seller ID for the relevant marketplace
Before Connect closes
Linnworks
API token generated from the Linnworks settings panel (Application ID and Application Secret)
Before Connect closes
Xero
OAuth 2.0 connection authorised under an account with Adviser or Standard role access
Before Connect closes
Slack
Name of the buying team channel and permission to install an incoming webhook or bot integration
Before Connect closes
Google Sheets
Link to the existing master sheet (or confirmation to create a new one) and edit access granted to the FullSpec service account
Before Connect closes
The one configuration decision you must confirm before Connect closes: Linnworks must be designated as the single source of truth for on-hand stock quantities. If Shopify or Amazon Seller Central also writes stock levels independently today, you need to confirm whether those independent writes will be disabled or whether a tiebreaker rule is needed. The sync logic cannot be finalised until this is resolved. Please raise this with your fulfilment coordinator (Dana Kriel) and confirm in writing to the FullSpec team before the end of the Connect stage.
04Your role once live
Once the automation is live, your team's involvement in inventory sync drops from nine hours a week to exception review only. The table below sets out what each party is responsible for on an ongoing basis.
Role
Ongoing responsibilities
What you no longer touch
You (business owner and fulfilment team)
Review anomaly flags in Slack or Google Sheets when a negative-quantity result is held for human approval. Update reorder threshold figures in Google Sheets when buying decisions change. Notify FullSpec if a new sales channel or warehouse location is added.
Manual stock counts across platforms, tab-switching between Shopify and Amazon to update quantities, spreadsheet calculations, batched return restocking, end-of-week Xero reconciliation, and ad hoc Slack messages to the buying team.
FullSpec
Monitor automation run logs, resolve any API connectivity issues, apply fixes if a platform updates its API schema, and provide ongoing support via support@gofullspec.com. Proactively alert you if run volumes or error rates shift outside expected ranges.
Not applicable.
Launch PlanPage 3 of 4
FS-DOC-01Operations
05What success looks like
The table below describes what you should observe at each milestone after go-live. Use these as your reference points when reviewing the automation's performance with your team.
Timeframe
What to expect
Sign of success
Week 1
The automation runs on every live order, return, and purchase receipt. You will see timestamped rows appearing in the Google Sheets audit log and Slack alerts firing when SKUs hit reorder thresholds. One or two anomaly flags may appear as edge cases surface for the first time.
All channels show matching stock quantities within 2 minutes of a triggering event. No manual platform logins required by the fulfilment team.
Month 1
The fulfilment coordinator's weekly hours on inventory tasks drop significantly. Xero is updated continuously rather than in a Friday batch. The buying team receives structured, consistent Slack alerts instead of ad hoc messages.
Oversell incidents fall to near zero. Weekly sync labour cost drops from approximately $405 to approximately $22. Finance reconciliation requires no back-and-forth with fulfilment.
Month 3
The process runs without active attention. Reorder thresholds are tuned based on real data patterns. Any new SKUs added follow the same sync rules automatically. Approximately 113 hours of staff time have been returned to higher-value work.
Annualised saving tracking toward $21,000. Payback period of 4 months reached. Team confidence in stock figures is high enough that manual spot-checks have stopped.
Next step: confirm your tool credentials and the Linnworks source-of-truth decision with the FullSpec team so the Connect stage can close on schedule. Send everything to support@gofullspec.com and FullSpec will acknowledge receipt and confirm the build start date within one business day.
Launch PlanPage 4 of 4