209 practitioner guides on ERPNext, Frappe, commerce and automation, written by the team that ships them.
A complete chart of accounts for Indian companies — 118 accounts, importer-ready for ERPNext, with every ledger mapped to its Schedule III head. GST ledgers named to match india_compliance, the MSME payables split built in, and the import sequence that avoids the ledger-entry lockout.
The GST e-invoice limit has been ₹5 crore AATO since August 2023 — and it binds from the first FY you ever crossed it. Find your exact liability date, check the exemption list, price the exposure of skipping it, and put a threshold watcher on ERPNext before 1 April 2026 sweeps in the next batch.
The e-way bill limit is ₹50,000 inter-state — but your state decides the intrastate line, and five states set it at ₹1 lakh. State-wise thresholds, the 200 km/day validity maths, the 8-hour extension window, Section 129 detention costs, and the ERPNext expiry watch that keeps trucks moving.
A comparison of 15 ERPNext implementation partners in India by Frappe tier, city and specialisation — written by one of the firms in it, and saying so.
Frappe partner requirements include $100/month of client spend on Frappe Cloud. We meet the other two criteria. Here is why we decline that one.
Can ERPNext run a 500-user Indian enterprise? Who already does, where it scales, where it doesn't, and the 5-year TCO against SAP — an honest CXO guide.
Eight GST changes land with FY 2026-27 — the ₹5 crore e-invoice sweep, LUT renewal, fresh document series, GSTR-9 late-fee blockers, GTA declarations and more. An impact checker shows which ones hit you, and a cutover kit gets ERPNext ready before 31 March.
Every mandatory field on a GST tax invoice under Rule 46, with free Excel, Word and PDF templates you can use today — plus a copy-paste ERPNext print format with the signed e-invoice QR wired in, and the serial-number and HSN-digit rules that trip businesses at audit.
Medusa v2 in practice — the modules you get free, the four places your code hooks in, and the honest boundary where the commerce layer stops and your problems begin.
Shopify Payments does not work in India, so you pay a platform fee on top of a gateway. But COD is exempt and UPI carries no bank MDR — which means your payment mix decides the bill, not your plan.
Shopify does not split CGST and SGST, does not derive place of supply, and has no IRN. Nine of the sixteen mandatory Rule 46 fields have no native equivalent — here is exactly what is missing and what it costs.
How to migrate from Shopify to Medusa.js without wrecking your SEO or your customer base — what exports, what doesn't, the forced password reset, phased cutover, and real timelines.
Every Shopify fee in one place — plan, platform transaction cut, gateway MDR, apps, currency conversion and chargebacks — with worked three-year totals for India and the US.
The real reasons merchants move off Shopify in 2026 — fees that scale with revenue, a locked checkout, undocumented catalogue limits, and data you cannot fully export. Plus the honest case for staying.
On Frappe v15, build_match_conditions() returns an empty string when a user holds User Permissions but their role grants neither read nor select. Callers read empty as 'no restriction' and the report shows every row. Here is the trace, the version nuance, and the fix.
Frappe's System Health Report reports the scheduler as Process Not Found whenever the scheduler runs in its own container. It is a file-lock bug, not an outage. Here is why it happens, how to prove your scheduler is actually alive, and what the unmerged upstream fix does.
Strict User Permissions plus a Company User Permission set to Apply to All Document Types empties the Purchase Invoice list with no error. ERPNext fixed it with a one-line JSON flag in v15.116.0 and v16.27.0 — which means Asset and Shipment still carry the identical bug.
Every PDF download returns 504 on frappe v16.24.0–v16.24.2. A directory path reaches read_file, kills the CDP reader, and blocks the worker forever. Here is the version boundary, the fix, and how to tell this apart from the Print Designer chromium-path bug.
Three real Frappe/ERPNext filter-shape bugs, each with its exact version boundary. One shipped in v16.14.0 and was fixed in v16.21.0. One is open but only reachable from custom code. One never affected a shipped v16 release at all.
medusa db:migrate stops dead after creating the migrations table, with no error and no CPU. The confirmed cause is Medusa forcing SSL on any non-localhost host, plus a knex pool that never rejects. This guide separates that from the still-open ARM64 case and gives you a real diagnosis playbook.
Medusa v2 confirms a cart against summed stock across every linked location, then reserves the whole line from location_ids[0]. The order is created first, so checkout fails after the order exists. Here is the source-level proof, the two fixes that provably cannot work, and the one that does.
Medusa v2's Workflows SDK rolls back database writes when a step fails. It cannot un-emit an event, un-send an email, un-write to your ERP, or un-charge a card. Three verified bugs in v2.18.0 show exactly what that costs, and how to build around it.
ERPNext Payment Reconciliation times out when matching 2000+ payments against 5000+ invoices. This guide fixes the timeout with batch processing, adds auto-matching rules, and sets up a daily scheduled reconciliation job.
ERPNext Production Plan's 'Get Items from Sales Orders' misses partially delivered orders, shows wrong pending quantities, and ignores material availability. This guide fixes the three breakpoints with interactive diagnostics and working Python scripts.
ERPNext Quality Inspection blocks Stock Entry submission when readings fail — but only if configured correctly. This guide covers QI template setup, auto-triggering on manufacture, rejection workflows, and the common configuration gaps that let defects through.
Medusa v2 checkout slows to 8+ seconds when your store has 1000+ product variants. The root cause is a quadratic variant pricing lookup. This guide diagnoses the bottleneck and fixes it with database indexes, caching, and pagination guards.
Medusa v2 has no built-in COD payment method or Shiprocket fulfillment module. This guide builds both from scratch — the COD payment provider, Shiprocket API integration, RTO handling, and the webhook pipeline that keeps order status in sync.
Showing 24 of 206 articles