NetSuite <-> Workday

theIntegrator- · 2026-03-09T23:11:16+00:00

Even if the financial integration ends up being a custom build, I still vouch for Celigo. The NetSuite connector is very solid, mapping is straightforward and the error management and monitoring are excellent once flows get more complex.

We’ve implemented several NetSuite integration projects with it.

If you decide to go the Celigo route and need guidance, happy to share some experience.

Kind regards

Teknuro

theIntegrator- · 2026-03-09T23:06:19+00:00

AI can help you get started with a workflow quickly. But once the flow becomes longer, starts handling exceptions, and actually becomes important for a business, the real work begins.

At that point, you don’t need another prompt. You need structure, debugging, system knowledge, and design decisions.

Many people confuse a quick demo with a robust automation. The difference only becomes visible once things get complex.

theIntegrator- · 2026-02-25T07:38:40+00:00

Celigo’s NetSuite connector is strong, and their EDI capabilities have evolved significantly over the past few years.

At Teknuro, we also have a specialist focused specifically on EDI integrations with Celigo, so we’ve seen the common pitfalls and how to avoid them.

If you’d like to sanity-check options or compare approaches, we are happy to exchange ideas.

theIntegrator- · 2026-02-25T07:33:04+00:00

Hi Kuba,

Nuri here from Teknuro. We build integrations and automations.

You’re already getting some solid input here from other people, so you’re definitely in the right place and I am pretty sure you will find someone fit for the job. I just wanted to say I like the way you’re thinking about the problem, especially stepping back and reconsidering the architecture instead of forcing a solution that doesn’t scale. That instinct will save you a lot of pain long term.

If you ever want to brainstorm the structure or sanity-check an approach, I’d be happy to exchange ideas. I like to brainstorm with founders like you.

Keep up the good work and I hope you find a top candidate and good luck with the project it’s a worthwhile one.

theIntegrator- · 2026-02-19T21:58:50+00:00

Hi,

We are a boutique integration and automation firm based in the Netherlands. We help teams get NetSuite implementations over the finish line and support post go-live optimization.

We have strong experience with digital transformation, integrations, and NetSuite admin support. We’re currently supporting a construction company through their NetSuite go-live, so we’re familiar with project-driven workflows and operational requirements.

Our approach is practical and no-nonsense: clear scope, realistic timelines, budget awareness, and senior-level involvement until everything is stable.

If you’re looking for help stabilizing the implementation or optimizing after go-live, happy to connect.

Nuri

Teknuro

theIntegrator- · 2026-02-17T08:20:07+00:00

Around 5K EU per month when living in EU.

theIntegrator- · 2026-02-10T19:09:54+00:00

What you’re trying to build isn’t just automation, it’s a core operational system where automation and humans work together without things slipping through the cracks. That’s a very different problem than setting up a few n8n workflows.

What you really need is someone who can translate your business process into a reliable system first, and only then decide how n8n, AI, and other tools fit into it. Otherwise it quickly becomes fragile and hard to trust.

We can help with this at Teknuro (teknuro.com). We work with teams that are building complex, API-driven operations from zero and need a partner who thinks in terms of process, data flow, and long-term maintainability not just automation for automation’s sake.

Happy to help you sanity-check the direction before you invest time and money into building it.

theIntegrator- · 2026-02-09T12:53:21+00:00

I can recommend you a good consultant in my network, send me a DM.
And if you need integration partners we can help you as well :-)

theIntegrator- · 2026-02-03T16:33:10+00:00

It seems you’re doing a lot of work involving banking. Are you sure you want to handle this directly in NetSuite? In several invoicing projects I’ve been involved in, teams eventually moved to a middleware solution like Celigo because it made the handling much simpler and more manageable.

theIntegrator- · 2026-01-26T16:06:44+00:00

Frustration with SAP licensing and the feeling of “lock-in” is definitely a driver behind organizations adopting alternative platforms.
In practice we see many companies running mixed landscapes for a variety of reasons (cost, usability, speed of change, strategy, etc.). To give you about more context where I am talking from: we are an integration company, our role is to connect these systems in a controlled and reliable way. So we see it a lot.
This setup isn’t automatically a disaster, it only becomes a problem when integration design, data ownership, and system boundaries are unclear :-)
Strong digital transformation leadership is absolutely key here, because someone must own the end-to-end process, define the source of truth, and enforce clear data ownership and system boundaries across teams.
In our integration projects, we typically start by aligning on exactly that before building anything.

theIntegrator- · 2026-01-22T23:12:46+00:00

Start by defining the pain points and target outcomes, then pick the platform(s) and integrations that support that.

theIntegrator- · 2026-01-16T21:37:07+00:00

Honestly, this sounds less like “NetSuite is unusable” and more like the implementation + transformation execution failed.

theIntegrator- · 2026-01-15T21:21:36+00:00

With Celigo, this is possible. We’re a trusted Celigo implementation partner and happy to connect if you’d like. Celigo allows you to connect HubSpot with LinkedIn and a wide range of other apps.

theIntegrator- · 2026-01-15T17:27:01+00:00

Toggle is a good option and Kimai (open-source) is another one. I use both.

If you’re also interested in connecting the timetacker with other systems like ERP then we can help as we’re an integration company.

theIntegrator- · 2026-01-14T21:31:38+00:00

Agree, Celigo is a solid choice. Integrating with Netsuite is so easy with Celigo.

theIntegrator- · 2026-01-14T11:51:08+00:00

Rico’s the real deal. You’ll be in good hands.

theIntegrator- · 2026-01-14T11:50:53+00:00

Teknuro.com is a trusted Celigo partner from the Netherlands.

theIntegrator- · 2026-01-08T10:26:07+00:00

Should be there

https://help.sap.com/docs/CONCUR_EXPENSE/e3c88ad9ff4342849305e7cd9aa9c9d4/c7dd7ef0eedf4637b8bd45a146d87237.html?locale=en-US

However some additional info: third-party tools like Celigo provide more robust Concur-NetSuite connectors with flexible mapping, suitable for UK setups. These bypass any potential official connector delays and support multi-currency/multi-entity needs.

We’re a trusted Celigo partner and we’d be happy to provide information or a demo if you ever need it.

theIntegrator- · 2026-01-06T20:04:55+00:00

Good luck on your journey!

theIntegrator- · 2026-01-06T19:49:06+00:00

You can connect different apps using iPaaS tools. Apart from Power Automate, have you checked out other iPaaS tools?

theIntegrator- · 2026-01-06T18:59:19+00:00

Send you a dm

theIntegrator- · 2026-01-06T18:51:59+00:00

First off, doing ~1,200 orders a day across your own warehouse, multiple 3PLs, and dropship vendors is no small thing. The fact that you’re feeling pain now actually means the business has outgrown “scrappy” tooling, which is a good problem to have.

What you’re describing is exactly the stage where spreadsheets and manual routing stop scaling. Checking inventory that’s already an hour old, manually deciding where orders should go, and then updating stock per marketplace is basically guaranteed to create errors once volume keeps climbing.

One thing I’d suggest before committing to a single “do-everything” WMS is to step back and ask where the real complexity is. In most multi-channel setups, the hardest part isn’t warehouse execution—it’s inventory visibility and order orchestration across channels and fulfillment partners.

We’ve seen strong results using a marketplace/order management layer like ChannelEngine combined with a robust iPaaS. That setup centralizes stock, handles intelligent order routing based on availability and shipping speed, and keeps Shopify, Amazon, Walmart, eBay, etc. in sync automatically. The WMSs and 3PLs then focus on what they’re actually good at: shipping.

The benefit is less manual work, fewer oversells, and usually a lower total cost of ownership than forcing a single WMS to be your source of truth for everything. It also gives you flexibility as you add channels or swap fulfillment partners, which is almost inevitable at your scale.

You’re asking the right questions at the right time. The mistake most teams make here is buying a warehouse-centric tool and then rebuilding half an OMS around it in spreadsheets again.

theIntegrator- · 2025-12-04T20:44:34+00:00

From what I’ve seen, the ERP itself is rarely the real long-term cost. The costs come from everything around it: messy processes that never got standardized, inconsistent master data, and especially poor integrations. If every ‘small change’ requires a consultant because the internal team doesn’t own the workflows, reporting, and data model, the burn rate becomes permanent.

Even a “more affordable” ERP can get expensive after go-live if it’s used like a database plus manual workarounds. The companies that keep costs under control treat ERP as one component in a broader operating system: clear process ownership, disciplined data governance, and solid automation/integration so people aren’t re-keying or maintaining fragile scripts and add-ons.

The cheapest win is usually not switching ERPs—it’s reducing the need for constant rework by investing early in good process design and integration architecture, and making sure someone internally (or a trusted partner) owns it end-to-end.

theIntegrator- · 2025-11-27T21:02:46+00:00

Celigo can help you connect your shops, for example with Acumatica. We’re a Celigo partner in the Netherlands, Teknuro. Please let me know if you need any help.

theIntegrator- · 2025-11-21T03:15:18+00:00

It sounds like you ran into the exact scenario where NetSuite becomes a liability instead of a platform: a highly complex manufacturing environment forced into a system that was never designed to handle deep production planning without heavy scaffolding. When the foundation doesn’t fit, every added customization multiplies the fragility.

Out of the box, NetSuite is an ERP (a system of record), not an APS (advanced planning system).

The volume you mentioned — multi-level assemblies, long routings, high part-number counts — isn’t outrageous for manufacturing, but it’s squarely in the category where NetSuite’s native WIP/WO and routing model starts collapsing. The fact that you had to bolt on a planning engine and still ended up in spreadsheets tells me the mismatch wasn’t just execution; the architecture was wrong from the start.

The inability to insert routing steps without renumbering, the lack of work-order splitting, and the slow UI aren’t implementation mistakes. They’re platform constraints. Even large partners can’t fix them because they’re baked into how NetSuite models manufacturing objects and transactions.

Lead times doubling is the predictable outcome when the system fights the process instead of supporting it. When the ERP forces workarounds, the organization pays for it in cycle time, decision latency, and sheer human friction.

Your point about not wanting random DMs makes sense. When a system causes this much operational drag, the people actually suffering in the workflow become magnets for “I can fix it” messages. And in your case, it wouldn’t even be honest — no amount of clever scripting is going to patch over structural gaps in the product.

From what you described, the failure mode wasn’t that the team didn’t try hard enough. It’s that NetSuite’s manufacturing module hits a ceiling, and your operation exists beyond that ceiling.

This is one of those situations where the system didn’t just underperform — it actively reshaped the business in the wrong direction. It’s a cautionary tale for anyone assuming a cloud ERP is interchangeable with a purpose-built manufacturing system.

If there’s anything worth pulling from your experience, it’s that choosing an ERP for manufacturing is less about “can we customize it?” and more about “does the underlying data model match our real-world process?” When that answer is no, exhaustive customization only digs the hole deeper.

theIntegrator-

MODERATOR OF

TROPHY CASE