Frequently asked questions

Yes, and in aviation that combination is normal rather than unusual. We have built operations where repair work, parts supply, equipment hire and on-site service all run side by side, including businesses that trade under more than one name with separate customer-facing identities and separate accounts, while management still sees one consolidated picture.

That is the central problem of repair work, and it is one of the first things we solve. Findings recorded during teardown, including measurements and photographs, become the customer’s quotation directly. Where a single intake contains several units, each is assessed and quoted separately, so approved work starts immediately instead of waiting for decisions on everything else.

Yes, and for parts suppliers this is usually the deciding capability. Each individual unit carries its own photographs and its own certification documents, available internally and, if you want, to customers before they buy. Condition grading governs what is offered for sale, so units awaiting inspection or judged uneconomic to repair stay out of your published availability automatically.

Most aviation operations are live within 8–12 weeks, depending on how many services and locations you run. Everything is built and tested on a practice copy first, so your day-to-day work carries on untouched while it is prepared. Your team is trained before the switch, and we are on hand through go-live week and beyond.

Yes, and that is what the Connected Tools section above covers. Your own carrier accounts produce the labels and tracking, your payment provider handles card and online settlement including any surcharge you apply, your bank feed reconciles itself, and your accounting either connects or moves across with its history intact. If you use something not listed there, tell us and we will look at it.

Then we build the difference, which is how everything in Where Standard Systems Stop came to exist. We will also tell you honestly which of your requirements are already covered without custom work. Bespoke development should be the exception in your project, not the bulk of your invoice.

We stay. Aviation businesses keep changing: a new service line, a second site, a customer with different paperwork requirements, a report you now want every Monday morning. We keep refining the operation as those needs appear, with support arrangements matched to the cover you want. Our longest-running aviation relationships are measured in years.

MRO software is the system a maintenance, repair and overhaul operation runs on: one record per job that carries intake photos, teardown findings, the quote, parts, labour, certification and the invoice. The aviation version adds serial level traceability, so the history of a unit is never separated from the unit itself.

The best procurement setup raises purchase orders from teardown findings, against the job, not from a reorder report. Stock parts reserve themselves; bought parts receive straight to the serial. The buyer sees demand with context, finance sees commitment before the invoice, and nothing lands in a bin unclaimed.

The one technicians actually update at the bench. If logging findings, photos and hours takes longer than the paper it replaced, adoption dies and the data lies. We configure screens around the bench workflow first, then let the office consume what the shop floor records. Fit beats feature lists.

Start with the things generic ERP gets wrong. Ask whether the system holds versioned formulas rather than parts lists, whether it converts units of measure natively, whether a lot can be traced in both directions in one step, whether quality release actually blocks stock from moving, and whether safety data sheets and labels are version controlled against the formula. Then ask the partner to run one of your real products end to end on a demo instance, from raw material receipt through to the certificate of analysis.

Purchasing gets clearer once demand comes from the formula instead of from memory. Planning reads the recipe for every open batch, nets it against stock on hand and stock already on order, then raises the purchase requirement with supplier lead time built in. Each purchase order line carries the expected date, the supplier price against your standard cost, the incoming quality check and the lot numbers received, so a buyer can see what is late, what is short and what arrived off specification on one screen. Receipts post against the lot, which means the traceability record starts at the supplier rather than at the vessel.

Formula and recipe management with version control and approvals. Batch manufacturing orders that capture actual quantities and yield. Lot and batch traceability in both directions, with quarantine and release control. Unit of measure conversion between weight, volume and percentage. Quality specifications, test points and certificates of analysis. Shelf life, expiry and retest date handling, with defined routes for rework and reprocessing. Document control that ties safety data sheets and labels to the formula revision. Per batch costing that includes yield loss. And accounting connected to all of it, so inventory valuation and margin come out of the same record as production rather than from a separate spreadsheet.

There are two costs and most quotes blur them. The platform license is paid to the vendor: on Odoo, around $31 per user per month on Standard and around $61 on Custom in the United States, billed yearly. The implementation is separate and driven by scope: formula count, data condition, historical lot migration, and whether you need distribution as well as production. Published industry ranges for mid market chemical ERP projects sit roughly between $25,000 and $80,000, which is an industry estimate rather than a quote from us. We do not bill hourly. We scope, quote a fixed fee including migration, and run ongoing support on flat monthly plans.

Batch tracking, yes, and natively. Every receipt, internal move, production step and shipment carries a lot or batch number, so you can trace a finished lot back to the supplier drum or forward to every customer who received it. Quarantine holds unreleased material so it cannot be picked, and shelf life, expiry and retest dates sit on the lot itself. On compliance we are deliberately precise about what we do: we configure the system to support your OSHA, EPA and SDS process, holding hazard classes, storage rules, document versions and the evidence trail in one place. The system supports your compliance program. It does not replace it, and no software makes a plant compliant on its own.

Yes. Safety data sheets are held as controlled documents attached to the product and to the specific formula revision, so when a formula changes the matching SDS version travels with it instead of leaving the old one in circulation. The current document can be attached to shipping paperwork and to the customer record, and access can be restricted by role so only the people who own the document are able to replace it. As with all compliance work, we configure the system to support your SDS process. Authoring and approving the content stays with your EHS team.

Yes, and this is usually the single biggest change contractors notice. Odoo Analytic Accounting posts every timesheet hour, purchase order, supplier invoice and customer application to the project it belongs to. That means certified value, committed cost, actual cost and forecast cost to complete all sit on one view, updated as the work happens. Directors see margin by project and across the portfolio without anyone building a spreadsheet first, because a report that takes three days to assemble is a report about the past.

Most construction clients go live in 8 to 12 weeks, depending on how many projects are running, how much history has to migrate and how much of the process needs tailoring. The approach is designed to avoid a hard stop: we work in phases, keep your current way of working running while the new system is prepared, and only switch once your own team has run a live project through it and is comfortable.

Yes. Odoo supports multiple companies, multiple stock locations and multiple currencies as standard, so each site holds its own materials and each entity keeps its own books while ownership sees one consolidated position. Approval limits by value and role, standard project templates and standard cost heads are defined once at business level, so a manager moving between sites finds the same rules. That consistency is also what makes projects genuinely comparable.

Usually, yes. Banking feeds, payroll providers, estimating and takeoff software, scheduling tools, CAD and document systems and client portals can all be integrated so information flows once rather than being typed twice. We will also tell you honestly where an integration genuinely earns its place and where the cost of building and maintaining it outweighs the benefit.

By refusing to keep the programme and the money apart. The estimate becomes the budget, and every purchase order, subcontract package and labour booking reports against it. Commitment shows the moment an order is raised rather than when the invoice arrives, so cost to complete is a live figure and a slipping task carries its cost with it.

The best fit is the one that survives your worst site conditions, so judge candidates on offline capture and sync, how they handle drawings, and whether your measurement rules need configuration or real development. Cloud suits contractors because the business is not in the office. The honest limitations are connectivity, heavy document handling, and bespoke measurement, and we will tell you plainly when the fit is poor.

Yes. Our Education Management build most often runs on Odoo, and handles applications, enrollments, classes, teachers, timetables, assignments, grading, fee structures, transport, and notice boards, with student and parent portals on top. Odoo’s Accounting and HR modules handle the finance and payroll side, so the whole institution runs in one database. We also deliver on Sage, NetSuite, Microsoft Dynamics and ERPNext, and which one you land on is settled after we have seen your academic calendar and fee structures, not before.

Yes. We connect the platform to payment gateways for online fee collection, Google Workspace and Microsoft 365 email, biometric attendance devices, and external accounting platforms. We actively maintain Odoo-and-Xero workflows for an education-sector client today, so cross-platform financial reporting is familiar ground for our team.

Most institutions go live in 8–12 weeks, rolled out in phases so admissions and fee billing start delivering value while later modules are still being configured. Migration of student records and opening balances is part of the plan, and we time the cutover to your term boundaries, never mid-exam season.

Yes. The platform’s multi-company structure supports separate campuses with their own fee structures, staff, transport routes, and academic calendars, while analytic accounting rolls everything up into consolidated group reporting. Role-based access keeps each campus team focused on its own students, and leadership sees the whole network on one dashboard.

In practice they are the same thing. School management software, school ERP, education ERP, and student information system all describe one platform that centralizes admissions, student records, attendance, grading, timetables, fees, and reporting for an institution. “ERP” is the older term borrowed from manufacturing; “school management software” is the plainer modern name for it. What matters is not the label but whether every department works from a single database instead of separate tools.

Yes. Parents, students, and staff access their portals from a phone as well as a desktop, so guardians can check attendance, grades, and fee balances and pay online without visiting the office. Teachers can take attendance and review assignments from a mobile device, and announcements reach families through the notice board plus WhatsApp or SMS alerts.

Training is delivered by role rather than by module, so your admissions officer, bursar, and class teachers each learn only the screens they use. After cutover you get ongoing support, new module rollouts, and reporting refinements as the institution grows. More detail on our training and support plans.

A great deal, and that is exactly why it needs discipline. Fee structures, grade scales, academic terms, approval workflows, and report layouts are all configurable to your policies. Where we push back is on customization that simply recreates an old paper process in software. That inflates cost and makes future upgrades harder. Our customization approach favours configuring the standard platform wherever it will do the job.

Live dashboards covering enrollment counts, fee recovery, outstanding dues, staff costs, and programme profitability, per campus and per programme, refreshed as the underlying records change rather than compiled at month end. Where deeper analysis is needed we build it out in Power BI on top of the same data, so the board and the finance office are never arguing about whose figure is right.

Equipment, vehicles, machinery, event supplies, and property rentals. The same platform adapts to each, and we tailor the workflows to how your business actually operates.

Confirming a booking reserves the asset instantly, and every branch works from the same real-time availability, so sales can never promise equipment that operations has already committed.

Yes. Overdue returns are flagged and invoiced automatically, damage is documented at check-in with photos, and charges are offset against security deposits with a clear audit trail before the refund is processed.

Yes, a branded self-service portal lets customers browse availability, request quotes, sign contracts, view invoices, and pay online, capturing bookings around the clock.

Yes. You get company-wide inventory visibility, tracked internal transfers between branches, and delivery and pickup scheduling linked directly to rental orders.

It depends on fleet size, branch count, and finance complexity. We publish a tentative timeline in the first two weeks of engagement.

Food traceability software records the identity, quantity, source and destination of every lot you receive, make and ship, so a batch can be followed forward to every customer and backward to every ingredient. In practice that means a lot number applied at goods in, carried through production, and printed on the case, pallet and delivery note. The value is answering within the hour when a supplier notification lands on a Tuesday afternoon, with an answer that holds up when a customer or auditor checks it.

Honestly, it depends on what your operation actually needs, and anyone who names one system before asking is selling, not advising. The questions worth asking are whether it handles lot and batch traceability natively, whether it supports FEFO picking and catch-weight goods, whether recipes carry yield and loss factors, and whether the vendor or partner has actually configured it for a food or beverage operation before. Odoo covers all of that natively at most processing volumes, which is why it is our most frequent recommendation and where our bench runs deepest. Sage, NetSuite, Microsoft Dynamics and ERPNext are the other systems we deliver, and a neutral second opinion is reasonable before you commit. That is what an ERP consultant engagement is for if you want one first.

FSMA 204, the FDA Food Traceability Rule, asks businesses handling foods on the Food Traceability List to keep Key Data Elements at each Critical Tracking Event and hand them over as an electronic sortable spreadsheet within 24 hours of a request. A properly configured system holds that data and exports it in that shape. Compliance itself stays your program, so we configure the system to support your HACCP, FSMA and food safety process rather than claiming to make you compliant. In scoping we map your lot codes and critical tracking events, then build the records and export around them.

Yes. Lot and serial tracking is native to Odoo’s inventory and manufacturing apps, covering receipt, production, and shipment in one chain. That gives you one-up, one-back traceability and the ability to pull every affected batch and customer in a single query. The recall procedure itself, and the judgment calls inside it, stay with your QA team.

Allergens are declared on the item specification, so every recipe inherits the allergen profile of its ingredients and a supplier or formulation change flags every finished product it touches. Allergen runs can be sequenced after allergen free runs, with sanitation scheduled as part of the changeover instead of remembered. On the label side, artwork is tied to the product revision, so the approved label prints, and the nutrition panel is calculated from the recipe rather than retyped.

Yes. Expiry dates are tracked at the lot level, and picking rules can enforce first-expired-first-out instead of first-in-first-out, which matters most when a newer lot physically sits in front of an older one on the shelf. Catch-weight items get handled the same way, priced and shipped on actual weight rather than a nominal unit.

Yes. Each lot carries its production date and its removal, best before or expiry date, and anything made from that lot inherits the rule. Picking can be set to first expired first out so the warehouse ships the oldest saleable stock, and short dated lots stop reaching customers who need long life. Date codes and lot codes print from the record the traceability report reads. Stock approaching its date appears while it can still be sold, instead of surfacing as a month end write off.

Two separate bills, kept honest and separate. Our fee covers implementation and configuration: recipes, lot rules, allergen data, integrations, and training, agreed in writing after a workflow review, with no hourly billing. Odoo’s own licensing is paid directly to Odoo, from $31.10 per user per month on the Standard plan, US, billed yearly. The full breakdown is on our Odoo pricing page.

Yes. Catch weight products are ordered as a case or a piece but priced on actual weight. The system holds both units on the same line, captures the measured weight at pick or pack, and invoices from that weight, which removes the credit notes born of billing one weight and shipping another, and keeps inventory valued on what actually left the building. Meat, poultry, seafood, cheese and produce operations usually need this on day one, so confirm it during scoping rather than after go-live.

It runs in phases rather than to a fixed calendar promise: workflow review, traceability and recipe mapping, staged migration, floor training, then a phased go-live. You get a written timeline after the workflow review, once we know how many product lines, recipes, and locations are actually involved.

Two separate costs, and most quotes blur them. The platform license is paid to the vendor: on Odoo, around $31.10 per user per month for Standard and around $61.00 for Custom on the United States list, billed yearly. The implementation is the project itself, quoted as a fixed fee against a written scope, with no hourly billing including for data migration. Industry estimates commonly place a mid sized implementation in the tens of thousands of dollars depending on sites, integrations and data quality. Treat that as an industry range, and expect our figure in writing after a scoping session.

Yes. Formula-style bills of materials carry yield and loss factors, so a batch’s real cost reflects what actually comes out the other end, not what the recipe card assumes. That number feeds directly into landed cost and margin reporting.

Yes, in one system rather than two connected ones. Production, lot genealogy, and quality checks run on the manufacturing side, while route and wholesale selling, pricing, and fulfillment run on the distribution side, both reading from the same inventory and lot records.

A property management system runs hotel operations: reservations, the front desk, housekeeping. A hotel ERP runs the business behind them: the ledger, payables and receivables, procurement, stock, payroll and reporting. The PMS belongs to reception, the ERP to finance and ownership. Most properties need both, which is why connecting them matters more than choosing.

Yes. Accounting, purchase, inventory, point of sale and HR cover the hospitality back office directly, with reservation and housekeeping capability added on top, and the multi-company structure suits groups where each property needs its own books but the group needs one consolidated view. The platform decision comes after we understand your operation, not before: Sage, Oracle NetSuite and Microsoft Dynamics are the alternatives we deliver.

Most single properties go live in 8–12 weeks, phased so finance and procurement deliver value while other modules are still being configured. Groups take longer, driven mainly by how much the chart of accounts varies between properties. We time cutover to your own occupancy calendar and never during peak season or a major event.

Yes, and it is one of the clearest wins. Hospitality pay is complex: service charge distribution, multiple rates per employee, shift differentials, split shifts and seasonal contracts. We have built attendance-to-payroll flows end to end, including exports into providers such as ADP, so rotas and clock-ins reach payroll without a spreadsheet in between.

Yes. Bookings, commissions, cancellations, and channel adjustments are brought in and reconciled against what actually reached your bank, so commission leakage becomes visible rather than assumed. Distribution itself stays with your channel manager, which is the right tool for it. We make sure the money side agrees with it. See our integration services.

Dishes are built from ingredients with costed recipes, till sales draw stock down automatically, and stocktakes compare actual usage against theoretical. The result is a cost of sale you read weekly, with variance identifying the outlet and the item. When a supplier price moves, you see which dishes stopped paying their way.

We audit what you hold first: the current system, spreadsheets, and anything on paper, then clean and map it before anything moves. Migration runs in phases rather than one risky cutover, and every flow is validated on staging so you see your own records working before you depend on them. See our migration service.

Training is delivered by role rather than by module, so your receptionist, head housekeeper, chef and financial controller each learn only the screens they use, which matters in a sector with high turnover. After cutover you get ongoing support and reporting refined as you grow. More on our training and support plans.

It depends on the company. Asset carriers and brokers run McLeod, Trimble, Turvo, Rose Rocket or Alvys. Third-party warehouses run Extensiv, Logiwa, ShipHero or Deposco. Large shippers run Oracle Transportation Management, SAP or Blue Yonder. Nearly everyone also runs EDI, a carrier API and an accounting system that knows nothing about freight. That gap is where we come in.

We quote a fixed price against a written scope, and we do not bill hourly. What moves the number is the integrations, not the feature list: one clean EDI partner and one carrier account is a small project; nine partners each with their own spec, a legacy TMS with no API and freight audit is a large one. Published ranges run from roughly twenty thousand dollars to several hundred thousand.

Buy, if a product already does the job. Dispatch, driver settlement and warehouse execution are mature categories you will not out-build for the money. Build when the thing costing you margin is specific to your operation, or spans systems that will not talk to each other. The common outcome is neither: keep the specialist products, build the record and the connections holding them together. When shopping for a logistics software development company, the useful question is not what they can build, but what they would talk you out of building.

The system that holds units, leases, tenants and owners in one place and runs the money between them. Rent invoices generate from the lease rather than being typed each month, maintenance is logged against the exact unit, and owner statements pull each property’s income and fees into one report.

Two costs, worth separating. The licence, charged per user or per unit. And the implementation: configuration, data migration, integrations and training. The second is where budgets actually move. Published ranges are industry estimates, not a quote. We work on a fixed fee with no hourly billing, migration included.

Compare on what is expensive to change later. Does it handle your awkward lease types. Can it run multiple entities with consolidated reporting. Does it do trust and escrow accounting properly. Will it connect to your MLS feed and your ledger. Can you get your data out again.

In stages, with the old system still running. We extract units, leases and history, contacts, open balances, deposits and documents, load them into a test environment, and reconcile against the old system before sign-off. Most go live in 8–12 weeks, running both systems through one full billing cycle.

Yes, and the route depends on what your board exposes. A modern MLS API is cleanest, an IDX feed covers public listing search, and some boards still run RETS. We map the fields to your property records once and keep them in sync, pushing status changes back where the rules allow.

Most platforms offer some connection, though they differ on whether it runs one way or two. Said plainly: QuickBooks manages the ledger, not the property. Invoices, receipts and journals belong there; lease terms, unit history and owner charges stay in the property system. We build that split deliberately.

In most cases, yes. The counter runs in a browser and supports common receipt printers, barcode scanners, cash drawers and card terminals. We check your existing hardware during the audit and tell you plainly what will carry over and what will not, before you commit to anything.

Most single site retailers go live in around eight to twelve weeks. Multi store groups take longer overall, though we go live one store at a time so you are trading on the new system early rather than waiting for everything at once. The honest answer depends on how clean your product data is, which we assess in the first two weeks.

Yes. Multiple locations, companies, currencies and tax jurisdictions run in one system, with head office reporting across all of them. Each store can carry its own pricing and its own stock while still sharing a single product catalogue.

The till keeps working. The counter holds the session locally and carries on taking sales and payments offline, then syncs everything back to the central system when the connection returns. Nothing is lost and nobody has to write orders down on paper. You can see how we handle go-live risk across our client case studies.

Retail ERP is the system behind the till: one stock figure across stores and warehouse, purchasing and true landed cost, pricing and promotions, sales, and accounts that reconcile without a monthly archaeology dig. The point of sale takes the money. Retail ERP is what makes the rest of the business agree about what just happened.

By holding one stock pool that stores, the website and the stockroom all read and update. Buy online and collect in store takes the reservation off shop stock; a store return against an online order refunds and restocks correctly; orders ship from the branch that actually has the item. Without one pool, omnichannel is two systems disagreeing politely.

Price lists live in one place and publish outward: base, channel, member, and time-boxed promotions that start and end themselves. Margin is checked against real landed cost, so a promotion that would sell below water is flagged before it runs, and branches can hold local pricing without breaking the group view.

Start where the money leaks rather than with a feature list: stock accuracy across locations, true landed cost, promotion control, and how your point of sale will connect. Then test each candidate against those four. Asked for the best ERP for retail, our honest answer is that fit beats brand, and we will tell you when the system you already run is worth keeping.

Self storage software runs a storage facility from one system: live unit availability, online bookings, digital contracts, gate access rights, recurring billing and occupancy reporting. The point is one record per customer, so the website, the gate and the accounts stop disagreeing with each other. It replaces spreadsheets and disconnected single purpose tools.

Cards and direct debit mandates are stored with the agreement, so the first payment and every renewal collect on schedule. Failed collections retry automatically and surface the same day, while the balance is small. Refunds and deposit returns follow the same rules, and every movement lands in the accounts without retyping.

A tenant books a unit at 9pm, signs on a phone, pays and gets a gate code in minutes. After that, a portal handles invoices, payment details and shared access, and reminders arrive in the tenant’s own language. Fewer phone calls for them usually means fewer for your counter too.

Map the journey and remove the manual handoffs one by one: online booking that creates the contract, payment that issues the gate code, billing that raises itself, arrears that pause access, move outs that settle and re list the unit. Start where the most cash or hours leak, not with everything at once.

Self storage facility management software is the operator’s back office: pricing, contracts, collections, access rights, maintenance and reporting across sites. It is distinct from your public website, though the two should share one record. If the counter retypes what the website already knows, the systems are separate in the way that costs money.

The honest answer: it depends on whether you want to rent software or own a system. Per door platforms such as SiteLink and storEDGE suit standard operations, and smaller single site tools sold as mini storage software or storage rental software cover the basics for one facility. Custom builds on Odoo suit operators with their own model, multiple sites or pricing the platforms cannot express. Odoo is where we are certified and where most of these builds land, though we deliver the same on Sage, NetSuite, Microsoft Dynamics and ERPNext when a group already runs one of them. A short audit settles it quickly.

Look for role based permissions, a full log of who opened which door and when, payment details held by the payment provider rather than in spreadsheets, and reliable backups. Safety is mostly the software enforcing the contract: access that pauses when payment lapses and closes completely at move out.

Physical security is gates, locks and cameras. The software’s share of it is keeping access rights matched to the contract at all times: codes that work only for paid up customers, shared access granted and withdrawn deliberately, and an entry log your team can actually check when something looks wrong.

Mainstream platforms price per unit per month, so the bill grows with every door, and website, gate and accounting add ons stack on top; treat published figures as industry estimates. Building on Odoo, licensing starts around $31 per user per month and our work is a fixed monthly scope with no hourly billing.

Yes. This answer was pushed from Odoo through the review workflow and appears here automatically, grouped under its industry.

Start from where the money leaks, not from a feature list. Price the things that will hurt at double the volume: landed cost, credit control, multi-warehouse stock, and how orders arrive from your customers. Then check the system does them natively rather than by add-on. We run a short audit and will tell you plainly when what you have is worth keeping.

Wholesale distribution is buying goods in volume and selling them on to other businesses rather than to consumers. The operation is the margin: purchasing at the right level, holding stock without drowning in it, picking and delivering accurately, and collecting from trade customers who buy on credit. Software matters here because every one of those steps hands off to the next.

We stay. Businesses change: a new warehouse, another sales channel, a report you now want every Monday. We keep refining the system as those needs appear, with support packages to match the cover you want. Most of our clients are still working with us years after go-live.

Yes, and for importers it is usually the biggest single win. Freight, customs duty and clearing charges get added onto the cost of the goods in that shipment, so the cost against a product is what you actually paid to land it on your shelf.

Yes. Each customer gets a credit limit, and if they are over it the order is held rather than shipped, it goes to a manager, who approves or declines it, and the decision is recorded. Your credit policy then applies to every order automatically, instead of relying on someone remembering to check the account first.

Yes. That is exactly what the Connected Tools section above is about. WooCommerce and Shopify stores, UPS and freight carriers, payment gateways, QuickBooks and Xero, label printers, Google Sheets and WhatsApp all join to your system so information flows automatically. If you run something not listed, tell us: if it has a way to connect, we can almost certainly join it.

Then we build the difference. Every fix in Six Problems Every Distributor Knows above exists because a wholesale client needed something no product offered. We will also tell you honestly which of your requirements the standard setup already covers, custom work should be the exception, not the invoice.

Most distributors are live in 8–12 weeks, depending on how many warehouses and sales channels you run. Everything is built and tested on a practice copy first, so your day-to-day trading carries on untouched while it is being set up. Your team is trained before the switch, and we are on hand through go-live week.

No. If a tool is working for you, we connect it rather than replace it. Your store keeps running, and orders, stock and invoices flow between it and Odoo automatically. If you would rather bring your books into one place, we migrate QuickBooks or Xero across without losing history. Your carriers connect too, so labels and tracking are produced for you.

What kind of task is this?

Problem

What was actually causing it?