Sound familiar?
What companies running SAP tell us before a project starts.
- Orders from our web store are retyped into SAP by hand each morning.
- Sales wants stock and customer balances, and every request goes through one person.
- Month-end reports are exports that someone pastes into Excel and reformats.
- Our SAP consultant is costly and slow for small changes, so we live with workarounds.
- The CRM and SAP disagree on who the customer is.
What we build
Each one is a working piece you can open and check when it's done.
Web store orders into SAP
Orders, customers and payments from Shopify or WooCommerce created as sales documents through SAP's service layer or APIs, with failures listed for review.
API integrations and data sync QuickBooks, Xero and HubSpot integrationsStock and price back to the store
Availability and price lists pushed out of SAP on a schedule, so the store stops selling what the warehouse does not have.
API integrations and data sync ETL and data pipelinesCRM and SAP in agreement
Customer and contact records matched between the two, with one system named as the source for each field and conflicts queued for a person.
CRM setup and lead pipelines QuickBooks, Xero and HubSpot integrationsReports people can open
Sales, open orders, receivables and inventory from SAP data into a dashboard or a refreshed spreadsheet, without a login to SAP.
Dashboards and reporting ETL and data pipelinesScheduled data exports
Files in the layout your bank, carrier, auditor or partner expects, produced on schedule and delivered to a folder or by email.
ETL and data pipelines Python scripts and utilitiesExcel tools for SAP users
Upload templates that validate rows before they go in, so mass updates to items or prices are checked first.
Excel and VBA toolsWhat we connect it to: Shopify, WooCommerce, Salesforce, HubSpot, Excel, Power BI, Tableau, Microsoft Teams.
Industries that use it: Manufacturing, Wholesale, Logistics, Ecommerce.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Wholesale web orders into Business One
Example: a distributor takes orders on a web portal. Each paid order creates a sales order in Business One, and any item that fails to match is listed in a morning email.
Business One service layer, portal webhooks, PythonExample project
Open orders report for sales reps
Example: a manufacturer's reps want to see their customers' open orders and balances on a phone. A nightly extract feeds a dashboard filtered by territory.
S/4HANA OData, database, dashboardExample project
Price list upload checked in Excel
Example: a purchasing team updates hundreds of item prices each quarter. A workbook checks codes and formats, then writes the clean file the import expects.
Excel VBA, SAP import templateQuestions people ask first
Do you replace our SAP partner?
No. They look after SAP itself. We build the connections and reports around it, and work with them where changes inside SAP are needed.
Do you need access to our live system?
We prefer a test company or sandbox, and read-only access for anything that only reports. Writing into live data comes after you have checked the results.
Which versions do you work with?
Business One and S/4HANA are the focus. We confirm your version and what interfaces it exposes during the first review.
How do we start?
Tell us which two systems need to share data, or the report you wish existed. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com