




















































































Centric WMS provides warehouse management software for distributors, 3PLs, and manufacturers, supporting inventory, picking, packing, shipping, and yard management.
Have any questions? We’re here to help You
Connection credits are Makini's billing unit. Each system integration consumes a specific number of credits based on complexity. Systems are divided into three tiers: Tier 1 (simple systems like cloud CMMS), Tier 2 (mid-complexity ERP systems), and Tier 3 (complex systems like SAP). On-premises installations require double the credits of their cloud equivalents. For example, a cloud SAP S4/HANA connection might use 4 credits, while an on-premises SAP ECC installation uses 8 credits. Connection credits are consumed when you establish a connection and are returned to your pool when you disconnect. This allows flexible allocation across customers—you're not locked into specific connections.
Data synchronization frequency is configurable based on your requirements. For real-time needs, Makini supports webhook-based synchronization where changes trigger immediate updates. For scheduled syncing, common intervals range from every 15 minutes to daily, depending on data volume and business requirements. The initial sync after connecting a system retrieves historical data based on your configuration—typically 30-90 days of historical records. Subsequent syncs are incremental, retrieving only records created or modified since the last sync. Sync frequency doesn't affect pricing. You can also trigger manual syncs on-demand via API when needed for specific workflows.
Connection-specific errors often relate to system configuration, permissions, or connectivity issues. Common scenarios include: the system is offline or unreachable, credentials have expired, API rate limits on the source system, or permission changes in the source system. Use the connection status endpoint to check connection health before making API calls. Implement circuit breaker patterns—if a connection repeatedly fails, temporarily stop making requests to avoid cascading failures. Log connection-specific errors separately to identify problematic connections. When errors occur, check if the issue affects all operations or specific entity types, which helps narrow down permission or configuration issues. For on-premises systems, verify network connectivity and firewall rules. Contact support if connection errors persist, providing the connection ID and affected operations.
Makini provides tiered support plans. Standard support includes email support with business hours response times, access to documentation and knowledge base, and webhook notifications for issues. Extended support adds direct access to our engineering team, faster response times including after-hours support for critical issues, proactive monitoring and recommendations, and assistance with custom development. Enterprise support includes dedicated support contacts, participation in architecture planning, quarterly business reviews, and priority feature requests. All plans include access to our API documentation, authentication guides, and community resources. Support hours can be added to any plan based on your anticipated needs.
