Third-party costs we disclose but don’t control
“No hidden fees” has to cover more than our own invoices. Every enterprise build carries third-party costs that are not Elogic service fees but are part of your total budget — so we treat them as part of the disclosure, not someone else’s problem. During discovery we surface all of them, model them into the 3-year TCO, and apply no markup: you either contract directly with the vendor (we facilitate procurement) or the cost passes through exactly as invoiced.
The categories to budget for: platform and SaaS license fees (Adobe Commerce, Shopify Plus, BigCommerce, Salesforce Commerce Cloud, commercetools — each platform name links to our published pricing guide); hosting and cloud infrastructure, including CDN and WAF; paid extensions, modules, and apps; attached SaaS services — search, marketing automation, reviews, loyalty, personalization, tax engines, fraud screening, and ERP/PIM/CRM connectors or iPaaS middleware; payment processing fees; SSL and domains; and periodic platform version upgrades.
We don’t quote generic figures for these, and the reason is structural, not evasive: enterprise platform licenses are typically revenue- or GMV-based, and hosting, payment, and most SaaS fees scale with traffic, catalog size, and order volume. Most of these costs are recurring; some — certain extensions, version upgrades — are one-time or episodic. The honest answer is your number, modeled against your projected volumes during discovery — which is exactly what the TCO deliverable is for.