Skip to main content
The Feature Settings page — reached from the Settings & Config sidebar group — is where an administrator turns optional capabilities on or off and tunes the shared presets that the rest of the workspace reads. Every choice here is workspace-wide, not per-user: changing a toggle here changes what every user sees the next time they open the affected screen. Only administrators can open this page. This reference walks each card on the page in the order they appear in the app, and for every setting describes what it controls, what changes when you turn it on, what changes when you turn it off, the default it ships with, and any caveats worth knowing before you flip the switch. A note on scope. Most settings here are display or default-value choices and take effect immediately. A handful — the cost-sheet audiences list, the material-arrival gate, the packing and QC dropdown lists — change behaviour the system enforces or the rows the system creates from that point forward. None of these settings rewrite existing records, but a few do leave older records visibly out of step with a new choice. Caveat lines call those out one by one.

​
BOM

​
Allowed BOM item types

Choose which item types your team can add to a style’s : Fabric, Accessory, or Other.
  • Controls. Which type buttons appear in the BOM line editor on a Style’s BOM tab.
  • When a type is allowed. The button is shown and users can add new lines of that type.
  • When a type is disallowed. The button is hidden and no new lines of that type can be added.
  • Default. All three types allowed.
  • Caveats. Hiding a type does not remove or hide existing BOM lines of that type — they remain visible and editable on every style that already had them. The setting gates new lines only.

​
Cost sheet

​
Cost-sheet audiences

Choose which audiences each cost sheet is approved for: Customer, Factory, or Internal.
  • Controls. Which approval rows the system creates on every new cost sheet, and which audiences are valid targets when an operator exports a cost sheet.
  • When an audience is enabled. Every new cost sheet starts with a pending approval row for that audience, and the export action accepts it as a target.
  • When an audience is disabled. No approval row is created for that audience on new cost sheets, and the export action rejects it.
  • Default. All three audiences enabled.
  • Caveats. Disabling an audience does not remove approval rows already on older cost sheets — those rows stay where they are until the cost sheet is superseded. Order cloning copies cost sheets with fresh approval rows generated from the audiences enabled at the time of the clone.

​
Packing and QC option lists

Four dropdowns on the Style Packing and QC tabs are populated from lists you maintain on this card. Each list is an editable text area; enter one option per line and save. The four lists are:
  • The carton-packing method options.
  • The shipping-carton label options.
  • The carton-spec options.
  • The AQL level options for inspection.
For every list:
  • Controls. The values your team can pick in the corresponding dropdown on every style’s Packing or QC record.
  • When a list has values. Each line becomes a selectable option; the chosen value is saved on the style’s Packing or QC record.
  • When a list is empty. The dropdown opens to a blank picker — your team cannot select a value until you add lines back. There is no built-in fallback list.
  • Default. Each workspace ships with a starter set of options you can keep, edit, or replace. Review them on first setup and tailor them to the values your customers actually expect on cartons and inspection reports.
  • Caveats. Edits take effect on the next selection. Styles whose Packing or QC record already names an option keep that value even if you later remove the option from the list, so the saved record stays internally consistent.

​
PMS

A issued from a style pins specific BOM and cost-sheet versions and a factory. The two switches on this card decide whether the platform checks those pins before the MO is issued, and whether a missing or unapproved pin blocks the issue or only warns about it.

​
Enable pre-flight validation

Turn the pre-flight checklist on.
  • Controls. Whether the platform runs a pre-flight check when an operator issues a manufacturing order from a style.
  • When on. The platform checks that the MO’s pinned BOM version is approved, that the MO’s pinned cost-sheet version is approved, and that a factory is set. The check result is surfaced on the issue action — passes, missing pins, and unapproved versions all show per line. Whether the issue proceeds depends on the next setting.
  • When off. The MO issues with no pre-flight; nothing is checked, and nothing is surfaced.
  • Default. Off.
  • Caveats. Leave this off until your team’s BOMs and cost sheets reach approval reliably on time; otherwise every MO issue becomes a reminder to chase an approval. Turn it on once the approval discipline is in place, leaving the next setting off, so the team sees warnings without being blocked. The factory check is advisory only — it surfaces as a warning but never blocks issuance on its own.

​
Require pre-flight before generation

Block the MO issue when a pre-flight check fails.
  • Controls. Whether a failed pre-flight check blocks the issue or is treated as a warning.
  • When on. Issuing an MO whose pinned BOM or pinned cost sheet is missing or not yet approved is rejected on the spot with the failed checks named; the operator must approve and pin the flagged artifacts before the MO can issue.
  • When off. A failed pre-flight check is surfaced on the issue response as a warning, but the MO issues anyway. The team sees the warning and is expected to follow up.
  • Default. Off.
  • Caveats. This switch is disabled unless Enable pre-flight validation above is also on — the require gate has nothing to enforce while the check is off. Turning this on without an approval discipline in place will stop the team from issuing MOs that everyone expects to proceed; reach the warn state first, work through any surprises, then escalate to required.

​
Sample T&A

The Sample Time-and-Action (T&A) grid plans and tracks a style’s sample sequence — fittings, pre-production samples, the salesman sample set, bulk-cut materials, top-of-production, and the final sample chain — with planned and actual dates per milestone. It lives on the order’s Readiness tab and feeds the readiness engine. The two settings on this card let you turn the whole grid on for your workspace and, optionally, hide individual milestones from it.

​
Sample T&A enabled

Turn the Sample Time-and-Action grid on for the workspace.
  • Controls. Whether the Sample T&A grid appears on the Order Readiness tab, and whether the readiness engine evaluates sample milestones at all.
  • When on. The grid appears on every order’s Readiness tab; users can enter planned and actual dates per milestone with autosave; sample milestones contribute to the readiness result.
  • When off. The grid is hidden and the readiness engine skips sample milestones entirely.
  • Default. Off.
  • Caveats. The companion setting Disabled sample milestones has no effect while this is off — turn this on first.

​
Disabled sample milestones

Hide individual milestones from the Sample T&A grid.
  • Controls. A per-workspace list of milestones to suppress. Any milestone you uncheck here is removed from the grid and skipped by the readiness engine.
  • When at least one milestone is unchecked. Each unchecked milestone disappears from the grid on every order, and the readiness engine produces no result for it.
  • When everything stays checked. The full grid is shown and every milestone is evaluated normally.
  • Default. Everything checked — no milestones hidden.
  • Caveats. The grid shrinks silently. There is no banner or footnote telling your team a milestone has been hidden by workspace settings; coordinators will simply see a shorter grid. Communicate any change you make so the team knows why a milestone they expected to plan no longer appears. For what each milestone represents, see Samples and fitting.
Reorder and hide the items in the left navigation.
  • Controls. The order and visibility of the top-level items in the left navigation sidebar (and the mobile drawer).
  • When configured. The sidebar and drawer follow your saved order. Items you uncheck disappear from the link list.
  • When left at default. Every standard sidebar item appears, in the canonical order, with one exception: Order samples is hidden by default. Its standalone surface is the legacy customer-approval ledger (see Samples and fitting); tick it back on here only if your tenant still works that ledger.
  • Default. All items shown, default order; Order samples off.
  • Caveats. Two items — Dashboard and Orders — are core navigation and cannot be hidden. Hiding any of the others is presentation only: the underlying features remain reachable through deep links, cross-references from other pages, and search. Use this to bring the modules your team uses every day to the top and tuck the rest away. The items you can show, hide, or reorder are: Readiness, Quotations, Styles, Fitting, Order samples, PMS, Purchase orders, Inventory, Production, Shipments, Invoices, Accounts payable, Customers, and Reports.

​
Order cloning

Cloning an order is a shortcut for repeat business — duplicating an existing order’s header, styles, and (optionally) supporting records into a fresh draft. The two settings on this card set the default state of the include-toggles in the Clone Order modal. The operator running the clone can override either default per clone.

​
Clone includes BOM

Set whether cloning an order pulls each style’s BOM along by default.
  • Controls. The default state of the include-BOM toggle in the Clone Order modal.
  • When on. Each cloned order starts with the source order’s styles’ latest BOM duplicated as a fresh draft version, with lines, images, and colourways remapped to the new order.
  • When off. The cloned order has no BOM until someone adds one.
  • Default. On.
  • Caveats. A per-clone override is available in the Clone Order modal; this setting only chooses the default position of the toggle.

​
Clone includes cost sheets

Set whether cloning an order pulls each style’s cost sheets along by default.
  • Controls. The default state of the include-cost-sheets toggle in the Clone Order modal.
  • When on. Each non-superseded cost sheet on the source order is cloned as a fresh draft, with new approval rows generated from the audiences enabled in Cost-sheet audiences at the moment of the clone.
  • When off. The cloned order has no cost sheets.
  • Default. Off.
  • Caveats. Cloning with cost sheets on but BOM off produces cost-sheet lines whose link back to a BOM line is dropped, because there is no BOM on the new order to link to. The lines still carry their material descriptions, quantities, and prices, but the live link from a cost-sheet line to its source BOM line is gone. Avoid this combination unless unlinked cost-sheet lines are what you want.

​
Production, shipments, and dashboards

​
Material-arrival gate

Block the Cutting milestone on a factory order until the order’s received-material coverage meets your workspace thresholds.
  • Controls. A pre-cut check that compares received fabric and trim quantities on a against required quantities. If coverage falls below the thresholds set in your active readiness ruleset (defaults: 100% fabric, 100% accessory), the operator’s attempt to set the Cutting actual date is blocked.
  • When on. Trying to set the Cutting actual date on a factory order whose material coverage is short returns a red gate state showing per-line shortfall — required quantity, received quantity, and coverage percentage — and the thresholds that were applied. An authorised operator can override the block with a written reason; the override (who, when, why) is recorded on the factory order and clears subsequent attempts.
  • When off. Setting the Cutting actual date proceeds with no material check.
  • Default. Off — this setting can stop the floor team from cutting, so it is always opt-in.
  • Caveats. Leave this off while a workspace’s material-receipt discipline is still ramping; every block is a real, on-screen stop. Turn it on once your receipts are reliable, and confirm in advance who on the team is authorised to use the override.

​
Role-based dashboards

Send each role to a dedicated home screen instead of the shared one.
  • Controls. Where users land when they sign in or click Dashboard.
  • When on. Administrators and boss-tier users land on a boss home; merchandisers land on a merchandiser home; sales and finance roles each land on their own home, with the figures and reminders that match the work that role does.
  • When off. Every user lands on the shared dashboard, which still surfaces administrator- and finance-only widgets to the roles that should see them.
  • Default. Off.
  • Caveats. The new home screen takes effect at the user’s next page load.
Leave the Unified shipment read toggle off. It is internal and in progress, not a supported workspace feature. Enabling it silently changes the per-size quantities recorded on packing lists, invoices, the shipment-related dashboard reports, and the Style progress bar — with no on-screen indicator that the numbers have come from a different source. Do not turn it on.

​
Tech Packs

The Tech Packs module is the receiving side for a brand’s authored specification — a PDF, Illustrator (.ai), or Techpacker .tpv becomes a working style with its BOM, size specification, images, instruction-page attachments, and QC checklist in one confirmed injection. Your administrator may enable it here; it is available on certain plans.

​
Enable Tech Packs

Turn the Tech Packs module on for the workspace.
  • Controls. Whether the Tech Packs sidebar entry is shown, whether the upload and review surfaces are reachable, and whether the factory work-order PDF action appears on the MO tab of tech-pack-originated styles.
  • When on. The Tech Packs entry appears in the sidebar; any user in your workspace who can see the module can upload, review and inject a pack.
  • When off. The module and its surfaces are hidden; the factory work-order PDF action does not appear on any MO.
  • Default. Off.
  • Caveats. This capability is available on certain plans. If the plan does not include it, this setting has no visible surface even when the underlying toggle is on. The rest of the platform is unaffected by either state — a style created without a pack behaves identically to a style created before Tech Packs was enabled.

​
Product card PDF

The cards this PDF prints from live on Product Cards — the workspace’s list of every sample tag and the place new ones are created. The setting on this card chooses the workspace-wide layout the cards print to.

​
Product card PDF fields

Choose which fields appear on the product-card PDF (the four-up A4 sample-tag layout) and in what order.
  • Controls. The selection and ordering of fields shown on the product-card PDF.
  • When configured. The PDF shows only the fields you have ticked, in the order you have set.
  • When left at default. A standard seven-field layout is used: brand, style number, style name, season, fabric A, colour, and size.
  • Default. The seven fields above, in that order.
  • Caveats. The card has a reset-to-defaults button if you want to revert. The full set of fields you can include is: brand, season, style number, style name, sample type, size, fabric A, fabric B, fabric C, colour, country of origin, trim notes, remarks, and card date.