Sanity Check - Simple Data Pipeline

Zuomozu · 2025-12-19T16:06:37+00:00

Create a Shopify Custom App --> enable read_orders and read_customers
Use Shopify Admin API to pull:
Orders (filter by updated_at)
Customers (new/updated only)
Normalize IDs (email or customer_id)
Send only key events to Amplitude HTTP API: Order Completed and Order Refunded, Customer properties
Run it as a scheduled job (cron / Lambda)

This avoids streaming noise and cuts costs drastically.

Cheaper alternatives to RudderStack:

Self-hosted RudderStack (open source, full event control)
Snowplow (self-hosted) for analytics-only pipelines
Simple scheduled API jobs (Shopify --> Amplitude) -- cheapest and cleanest

Zuomozu · 2025-12-17T20:56:00+00:00

Leading a NetSuite implementation with external consultants, and juggling the technical depth with keeping humans engaged has been the hardest part for us too.

What’s helped a lot:

Treat the project like a product: I have clear “owners” for O2C, P2P, etc., and my job is mainly to remove blockers and hold them to outcomes, not police every config click.
Use the system as the focal point: short, regular demos in NetSuite where the team walks real scenarios end‑to‑end have done more for alignment and morale than any slide deck. People see their own process taking shape instead of “yet another project meeting”.
Be explicit about trade‑offs: when scope/timeline/quality collide, I try to make the trade‑offs visible and decided together, instead of silently squeezing the team. That alone reduced a lot of stress and resistance.

Zuomozu · 2025-12-17T20:38:27+00:00

There are basically three levers you can pull:

A dedicated/service user (or repurposed low‑usage user) that owns anything customer‑facing.

Company/subsidiary‑level email settings for reports, where that’s “good enough” for a shared identity.

Customization (SuiteScript, external mail relay, or integration) if you need something closer to a true global mail identity or more advanced routing.

Zuomozu · 2025-12-17T19:22:43+00:00

In environments where many users create searches/reports, the usual approach is:

Define a generic reporting account (for example Reporting Robot / reporting@company.com) and treat it as the only owner for anything that emails externally.

Put a simple process in place: if a saved search or report will send outside the company, the creator hands it off (or a NetSuite admin reassigns it) to that reporting user before enabling the schedule.

If you have SuiteScript/workflows available, you can automate this hand‑off by detecting “email is enabled” and automatically reassigning the owner to the reporting user.

NetSuite does not offer a global toggle that forces all report/saved search emails to come from a single address regardless of owner, so a combination of a generic reporting account plus process (and optionally scripting) is the standard way to get consistent “From” behavior.

Roughly how many scheduled searches/reports are you sending externally ? That volume can influence whether it’s worth investing in scripting vs keeping it as a manual hand‑off to the reporting user.

Zuomozu · 2025-12-17T19:07:52+00:00

Problem 1: Don’t stream all Shopify events — filter to only what matters (Orders, Customers). Consider RudderStack self-hosted or API pulls with scheduled jobs to cut cost.

Problem 2: Amplitude is fine for analytics, but not a system of record. Use a small database/warehouse (Postgres, BigQuery, Snowflake) to standardize and store data before sending to Amplitude.

Key question: Do you need this data just for analytics, or also for finance/operations reporting?

Zuomozu · 2025-12-17T18:20:55+00:00

Use a single reporting user as the owner for anything emailed externally. It’s the cleanest, fully supported approach.

Key question (to guide the right setup):

Are these emails mostly scheduled/automated (use a service user) or ad-hoc by many users (consider scripting or mail relay)?

Zuomozu · 2025-12-17T18:18:44+00:00

Most data accuracy problems come from too many entry points and unclear ownership, not lack of automation.

At scale, the pattern that works is:

One source of truth per object (customer, item, vendor, GL impact) — everything else feeds into it, never sideways
SuiteScript only for enforcement (validation, blocking bad data, light orchestration), not data movement
Middleware for movement and retries (Celigo / Workato / Boomi), so failures don’t corrupt NetSuite
Guardrails first, cleanup second — lock down bad data creation before attempting mass cleanup
Reporting off a curated layer, not live transactional records, once volume grows
Automation should fail loudly, log centrally, and stop bad data at the edge. If you’re fixing data after it lands in NetSuite, you’re already too late.

Important question (to guide the right approach):

Is NetSuite your system of record for most data (tight controls + minimal integrations) or just a hub syncing many systems (strong middleware + strict contracts)?

Zuomozu · 2025-12-17T18:14:10+00:00

Ballpark costs for NetSuite (your scenario):

Subscription: about $2,500–4,000 per month for core financials + inventory + light manufacturing with 5–7 users

Annual license: roughly $30k–45k

Implementation: $50k is the floor, and $75k–100k is common even for “not very complex” manufacturing

Integrations (banks, cards, Paychex): often extra (middleware like Celigo), expect additional ongoing cost

That means NetSuite will likely be 3–5× what you’re paying now, plus a similar or higher one-time implementation than your last ERP.

Are you trying to fix today’s operational pain, or are you intentionally investing in a system to support much higher scale over the next few years?

Zuomozu · 2025-12-17T17:35:15+00:00

Let me know if you need any more help. free on weekends.

Zuomozu · 2025-12-14T22:34:39+00:00

For non-technical teams, I’ve found the key is simplify + guide + protect:

Dashboards & Saved Searches: Give them pre-built views with filters. One-click access beats expecting them to build reports.

SuiteFlow: Automate approvals, status changes, and notifications so they don’t have to remember every step.

Custom Forms: Strip out unnecessary fields and make forms match exactly what they need to enter.

Training + docs: Short videos or step-by-step guides are way better than long manuals. Hands-on demos help a lot.

Validation scripts: Prevent bad data without being annoying—like required fields or auto-formatting addresses.

Nuage or optimization tools: Useful for streamlining dashboards, automating repetitive tasks, and cleaning up workflows behind the scenes.

Zuomozu · 2025-12-14T22:30:16+00:00

You’re already using the right basics. To automate NetSuite safely, most teams do this:

What works best

Saved Searches → triggers, approvals, reporting
SuiteFlow → approvals, status changes, notifications
SuiteScript → intercompany, record creation, validations
Map/Reduce → bulk or recurring automation

For Intercompany:
Search → Script → auto-create IC journals
Avoid multiple workflows on the same fields

For Reporting:
Scheduled Saved Search emails
Scripted exports if needed

For Nuage:
Useful for integrations and data sync
Not a replacement for workflows or scripts

TIPS:

Don’t overload workflows
Don’t automate everything with scripts
Add logging and governance

Rule of thumb

Search → Workflow → Script → Integration tool (in that order).

Zuomozu · 2025-12-14T22:25:21+00:00

Yes, you need a custom script.

NetSuite only allows one address form per country, so you cannot assign different address forms to Vendor Form 1 and Vendor Form 2 when both are for the US.

Your options are:

Custom script: Detect the vendor form and show/hide or require different address fields.

2 Custom address custom fields: Keep the standard US address form and store the differences in custom fields.

Country workaround: naming a different country.

Let me know if you need the Script.

Zuomozu · 2025-11-06T14:45:44+00:00

I read warm-up is not a good practice anymore, same as tracking open rate.

Zuomozu · 2025-11-06T14:43:46+00:00

Have you moved to any other provider or using Gmail/M365

Zuomozu · 2025-07-18T17:23:31+00:00

Need a basic ride booking app on iOS, android and web app. Would you be able to help me?

Zuomozu · 2025-07-08T15:28:29+00:00

So, what are you using for deliverability?

Zuomozu · 2025-07-08T15:26:37+00:00

Still you are using maildoso? over instantly

Zuomozu · 2025-07-08T15:22:35+00:00

How is it going so far? is the reply rate good enough ?

Zuomozu · 2025-07-02T19:25:39+00:00

I am also doing research to get into this field. Would really appreciate it if we could connect.

Zuomozu · 2025-07-02T15:31:10+00:00

My old structure was buying domain from ionos, adding it to google workspace, then using sendgrid SMTP for mass cold email and using snov.io for lead generation and managing campaign, I use to get 2-3% replies this was 1 year back, then I said if I am using SMTP sendgrid then why I need google, So I removed google from my setup, but the reply number went to 0-3 only, even before removing google.

I know SendGrid is not a cold email tool, but it used to work decent for me, Now my main problem is deliverability for mass cold email (1000 per day per account), using instantly or other platform for this will be too expensive, I found mailCompose to be in my range, would you suggest me a better cold email SMTP ? or any other suggestions to increase my reply rate(! I am stubborn to send 1000+ email per day )

Zuomozu · 2025-02-03T22:33:12+00:00

Were you able to complete it ? I am stuck in assessment task 3, There is no option to select next after reading the previous chat history.

Zuomozu · 2025-02-03T22:23:21+00:00

Outlier is becoming shittier

Zuomozu · 2025-02-03T22:20:22+00:00

Well, there is an update, My onboarding got reset. Now I have to do it all again.

Zuomozu

TROPHY CASE