Full-stack guides

Building a Reliable Data Pipeline (ETL) for Scraped Data

How I build a data pipeline for scraped data: extract, validate, clean, deduplicate, enrich, store. An ETL pipeline that survives dirty, changing data.

CRM, ERP and App Integration for Small Business: The Complete Guide

How to connect your CRM, ERP, website, and apps without manual data entry - a practical guide for Israeli SMBs with real pricing and step-by-step approach.

Connecting CRM and ERP to a BI Dashboard: A Practical Guide

Your sales data lives in the CRM and your financial data lives in the ERP, so nobody can answer "which customers are actually profitable?". Here is how to join both into one BI dashboard - the architecture, the real costs, and the mistakes that make these projects fail.

Connecting Your Online Store to an ERP: Shopify and WooCommerce to Priority, SAP B1 and Hashavshevet

Every online order that gets retyped into the ERP is a mistake waiting to happen. Here is how store-to-ERP integration actually works - which direction each piece of data flows, what breaks first, and what it costs to build properly.

Systems Integration for Israeli Businesses: What Connects to What

A reference for the software Israeli businesses actually run - Priority, SAP B1, Hashavshevet, Rivhit, Morning, Monday, WhatsApp Business API - what integration each one supports, how hard it is, and which connections are worth building first.

Priority ERP API Integration: A Developer's Field Guide

Priority has a genuinely good REST API, and integrations against it still routinely blow their estimates. The reason is never the API - it is that every Priority installation is customised. Here is what to check before you scope, and the patterns that hold up in production.

Israel Invoice (Allocation Numbers): What It Means for Your Systems

An engineering guide to building around Israel's invoice allocation-number requirement: where it sits in your issuance flow, the failure modes it introduces, and how to design so a tax authority outage does not stop you invoicing. Not tax advice - confirm the current rules with your accountant.

Priority ERP Webhooks: Pushing Events Out Instead of Polling

How Priority ERP webhooks actually work - where they are defined, how BPM rules fire them, what headers and JSON body arrive, the 7-day error log, and the retry problem you have to solve yourself.

Priority REST API: The Errors That Waste the Most Time

A troubleshooting reference for the Priority OData REST API - why errors come back as XML from a JSON API, the auto-unique key trap on PATCH, batch limits, authentication combinations that cancel each other out, and how to find real field names.

The monday.com API: What Actually Limits You Is Complexity, Not Calls

A developer's guide to the monday.com GraphQL API - the three required headers, the complexity budget that stops integrations before the daily call limit does, column_values as JSON strings, and how to size a sync that will not die at scale.

Syncing Priority ERP With Shopify: The Four Flows and Where They Break

Connecting Priority ERP to an online store is four separate one-way flows, not one integration - catalogue, stock, orders and fulfilment. Which direction each runs, which needs to be real-time, and the failure modes that cost real money.

Syncing monday.com With Priority ERP: Where It Actually Breaks

A field guide to connecting monday.com and Priority ERP - why two-way sync is almost always the wrong answer, the handover point that should be one-way, the complexity budget trap, and how to keep the two identity models from diverging.

SAP Business One Service Layer: A Developer's Integration Guide

How to actually integrate with the SAP Business One Service Layer - the Login handshake, the B1SESSION and ROUTEID cookies, the 30-minute timeout and error -5002, OData v4 vs the deprecated v3, and the batch pattern that keeps documents consistent.

Priority vs SAP Business One: An Integrator's Comparison

Not a feature checklist - a comparison of what each ERP is actually like to integrate with. Authentication models, how you discover the real schema, batch limits, event push, and the questions that decide which one fits.

From Excel to an Israeli ERP: When to Move and How to Move the Data

The signals that say a business has outgrown spreadsheets, why the data migration is the whole project, the four things Excel hides that an ERP will reject, and the parallel-run period nobody budgets for.

Connecting an Israeli ERP to Anything: The Decisions Before the Code

A hub guide to ERP integration in Israel - the four questions that determine cost, why field-level ownership beats system-level ownership, when to push and when to poll, and the reconciliation job that makes any of it trustworthy.

Comax Integration: Connecting a Retail ERP to a Store

Comax exposes web services at ws.comax.co.il authenticated with a login pair. What that shape means for your architecture, the four flows a retail integration decomposes into, and why the POS is the constraint nobody plans for.

The Fireberry (Powerlink) API: Records, Queries and the Token Trap

Fireberry exposes a compact REST API - four operations over a generic record endpoint. What that design means for your code, and why the token being tied to a specific user is the detail that kills integrations months later.

Zoho CRM Integration From Israel: The Data Centre Trap and What Follows

Zoho runs several regional data centres and each has its own API and OAuth domains. Using the wrong one is the first bug in most integrations. Then come the Israeli specifics: phone formats, Hebrew fields and connecting to local invoicing.

What Drives the Cost of a Systems Integration in Israel

No price list here - rates vary too much to be useful. What does transfer is the five factors that move an estimate by multiples, and the questions that turn an unpriceable request into a priceable one.

Validating an Israeli ID Number in Code: The Check Every Lead Form Needs

An Israeli ID number is nine digits ending in a Luhn check digit. How it is calculated, why zero-padding breaks code, and why it is not identity proof.

Preparing a Legacy System for Israel Invoice Without Replacing It

An older invoicing system can keep running when an allocation number is required. What it is missing, which fields to add, and how to build the middle layer.

ShipOS or a Direct Courier API: How to Decide Between a Delivery Layer and Your Own Integration

ShipOS is an Israeli multi-carrier delivery layer for online stores. When one integration is enough, and when a direct courier API is worth building instead.

HFD Integration: Turning Orders into Shipments and Statuses into Data

HFD is an Israeli e-commerce courier with same-day delivery and E-Post lockers. How to build a dispatch gate, map carrier statuses and store proof of delivery.

Cheetah Delivery: Creating Shipments and Tracking Them from Your Own System

Cheetah Delivery runs the Cheetah Shops pickup network. How shipments are created from your system, what connecting needs, and handling changes after dispatch.

Lockers and Pickup Points in Israel: Building Automatic Point Selection at Checkout

Choosing a locker or pickup point at checkout is a data problem. Where the point list comes from, what the order must store, and what to do when a point closes.

Israel Post vs Private Couriers: Comparing Integration Paths for an Online Store

Comparing Israel Post with private couriers for an online store: coverage, tracking granularity, proof of delivery, returns, and how the interface is obtained.

SHVA, EMV and In-Person Payments: What to Understand Before Connecting a POS

An Israeli card-present payment has five roles: terminal, Ashrait, Shva, acquirer and issuer. Who owns what, what you decide, and where a POS link breaks.

Yaad Sarig and Pelecard: The Israeli Payment Interfaces Nobody Writes About

Yaad Sarig and Pelecard run at thousands of Israeli businesses and are barely discussed. What each interface looks like, where its docs live, what to ask first.

Morning (Green Invoice) API 401 vs 403: Which One You Have and How to Fix It

A 401 from Morning is almost always an expired token - the JWT lasts one hour. A 403 is a missing permission. How to tell them apart and build refresh that does not break.

Priority OData Errors: Telling an Invalid Filter From a Permission or a Missing Record

Priority returns standard HTTP status codes, and since 19.1 the error body is JSON. How to read 400, 403, 404 and 429, and narrow a filter down to one clause.

Cardcom and Tranzila Decline Codes: Turning a Gateway Response Into the Right Action

Each Israeli gateway has its own response field and code dictionary. How to read a decline, why copied code tables are dangerous, and what is worth retrying.

Payment Declined: How to Read the Gateway Response Before You Charge Again

A decline response carries three codes, not one. How to read the network code, the advice code and the gateway code, and what to check before you retry.

Shopify or WooCommerce Returning 429: Building a Sync That Doesn't Get Throttled

Shopify's 429 carries a Retry-After header and a 40-request bucket; a WooCommerce 429 comes from the host, not from WooCommerce. How to read both and sync well.

SQL Deadlock and Timeout: Find the Contention Instead of Extending the Wait

Errors 1205, 1222 and -2 look alike in a log and mean very different things. How to tell a deadlock from a lock timeout from a client give-up, and find the contention.

Moving From Access to a Web System: Replacing the Database Without Breaking the Process Around It

A plan for leaving Access while the business keeps running: mapping what depends on the file, moving data to SQL Server, and what sets the cutover date.

When AI Writes Code That Moves Money: Tests, Environment Separation and Human Approval Before Production

AI-written code that touches charges needs financial correctness controls: environment separation, money-path tests, idempotency and daily reconciliation.

WooCommerce or Shopify in Israel: Choosing on Operations, Content, Payments and Ownership

Not which platform is better, but where stock actually moves, who gets told, and where your data sits. Compared on each side's documented state machine.

Wix or Custom Inventory Development: When the Store's Process Matters More Than the Site Template

Draw the inventory states your store passes through, then check whether the data model has a field for each. What has no field ends up in someone's head.