Settings

Open Settings from the sidebar. Most settings require the Admin role.

Regional settings

Two values, used app-wide:

• Timezone — controls how dates and times render in the Gantt and in tooltips. Working hours are read in each calendar's own time zone, as set on the calendar in Odoo; this setting is the fallback for a calendar that has none. Click Detect to use the browser's timezone, or pick the production facility's timezone explicitly.
• Date format — how dates are formatted. Four options: DD.MM.YYYY, DD/MM/YYYY, MM/DD/YYYY, YYYY-MM-DD.

Material supply

Stop counting an overdue purchase order after (days) decides what a purchase order line past its planned day is worth. Empty, the default, it counts as arriving today and the Materials page shows it in orange with the days it is late. With a number, a line more than that many days late is no supply for the run or for the Material column until purchasing gives it a date; 0 drops it the day after its date. A plant whose purchasing keeps dates current can leave it empty; one with old open lines wants a small number. The field takes a whole number from 0 to 365; anything else is named under the field and Save waits until it is put right.

Sale orders on publish

Every publish tells each sale order in Odoo when its manufacturing is now planned to complete: the finish of the last manufacturing order under it, sub-assemblies included. The connector writes it as a note in the order's chatter and keeps the date in Manufacturing complete (APS) on the order. Two settings decide who hears about it:

• Sale order note — nobody told writes the note and nothing else; mention the salesperson adds an @mention, and with it a notification, when the plan is later than the order's promised delivery date; activity for the salesperson opens a to-do instead. There is one open activity per order: it is brought up to date while the plan stays late, and marked done when the plan is back inside the promise. An order without a promised delivery date is never late, and an order without a salesperson gets the note alone.
• Report a move of at least one — day or week. A move inside the same day or week is remembered but not written about, so a plan that shifts by minutes leaves no trail. Pick week when delivery is promised by week. Days and ISO weeks are counted on the organisation's timezone above.

Odoo connection

Three fields:

• Odoo URL — full URL, no trailing slash
• Database — Odoo database name
• API Key — generated here, then pasted into Odoo

See Odoo connector for full setup steps and how to find your database name.

After saving, click Test Connection. A green tick means APS can reach Odoo and authenticate.

Auto-sync

Auto-sync is off by default. Enable it once your connection is working and you've run at least one successful manual sync.

• Enable automatic sync — switch on to run a background incremental sync at the chosen interval.
• Sync interval — 15, 30, 60 (default) or 120 minutes.

Each scheduled run is an incremental sync — only records that changed in Odoo since the last sync are fetched. The minimum interval of 15 minutes is intentional: more frequent polling stresses Odoo and the network for very little benefit.

Manual sync

Click Run Full Sync in Settings to trigger a one-off sync regardless of auto-sync settings. Use after big structural changes in Odoo, or when you suspect data drift. Incremental syncs only run in the background when auto-sync is enabled.

The sync runs on the server, not in the browser tab. The bar moves inside a stage too and says what it is working on and how far it has got. A large database can take longer than the ten minutes a browser request lasts; the page then says the sync is still running on the server and follows it to the end, and a second click changes nothing. Rows that did not change in Odoo are not written again, and only the BOMs your open orders can reach are read, which keeps a sync short.

When the sync ends the page shows the result. If a stage could not finish (Odoo did not answer, or the database was busy with another write for more than 15 seconds) the notice is yellow and names the stage and the reason; the other stages are done, and running the sync again picks the missing one up. A sync that has reported nothing for 15 minutes is taken for stopped: the page says so and Run Full Syncstarts a new one in its place.

Sync status

Shows the result of the most recent sync:

• Last sync — timestamp of the most recent successful run
• Records processed — how many rows were upserted
• Records skipped — rows ignored due to validation issues (shown as a warning badge)
• Sync running — live indicator if a sync is in progress right now

Billing

Pricing is per work center per month. APS counts the work centers it discovered during the last sync.

• NONE — before the first sync, no billing record yet. Full access.
• TRIALING — 7-day free trial, starts on first successful sync. Full access including publish.
• ACTIVE — paid subscription, full access.
• PAST_DUE — payment failed, in grace period. Still full access for now.
• SUSPENDED — grace period expired without payment. App is read-only and the API blocks most calls.
• CANCELLED — subscription cancelled. App is read-only.

The trial gives you 7 days from your first sync to evaluate everything — you can sync, schedule and publish back to Odoo during the trial. To continue past the trial, add a payment method via the billing flow in the app before the grace period ends.

Users & roles

Open Users from the sidebar to invite teammates. Three roles exist:

• Admin — full access including Settings and Billing.
• Planner — can run schedules, publish, edit scenarios. No Settings access.
• Viewer — read-only access to everything.

Invitations are sent by email. Invited users sign up with the same email address — they'll automatically join the organization on confirmation.

Danger zone

At the bottom of Settings. Destructive actions live here, such as deleting all synced data. Read each warning carefully — these actions cannot be undone and can disconnect you from Odoo.