VeraCore
بواسطة Advantive
VeraCore typical implementation process:
Discovery and scoping: Vendor and client define business goals, warehouse processes, integration needs (shopping carts, ERPs, carriers), data standards, and project scope.
Solution design: Map current and future workflows, configure OMS/WMS rules (receiving, picking, packing, billing), and plan integrations using VeraCore’s prebuilt connectors and Integration Hub where possible.
Environment setup: Install/host VeraCore, set up interfaces, VPN/Wi‑Fi, hardware (scanners, workstations), and configure initial connections to carts/marketplaces, shipping systems, and other key systems.
Configuration and data prep: Configure warehouse locations, items/SKUs, clients, user roles, and charging rules; cleanse and import product, inventory, and customer data; set up reporting and dashboards.
Integration and testing: Implement API/cart connectors, enter API keys in the hub, configure permissions, and then run integration, functional, and scenario-based tests across inbound, picking, shipping, and invoicing flows.
Training and documentation: Use VeraCore’s training programs and knowledge base to train super users and operations staff, with hands-on practice in a test environment and role-based documentation.
VeraCore can be heavily customized/configured to fit specific 3PL and fulfillment business needs across workflows, rules, data, and integrations.
Configure tailored workflows, rules, and automation per client or use case (e.g., different receiving, picking, packing, and shipping flows).
Use rules-based order management to route orders by channel, client, service level, or warehouse, and control exception handling.
Adjust warehouse processes such as putaway logic, picking strategies, kitting/assembly steps, and billing triggers.
Support multiple clients in a single warehouse, each with its own workflows, SLAs, inventory views, and reporting.
Provide client-specific portals with tailored access to orders, inventory, and reports.
Apply different billing rules, pricing structures, and contract-specific logic per client.
Configure items/products with custom attributes, kitting/BOM details, and warehouse-specific handling rules.
Track specialized attributes (e.g., lot, expiry, serials) and custom carton/packaging data where needed.
Use custom fields and comment/metadata fields via integrations (e.g., extra identifiers, instructions) to drive downstream logic.
Build custom/dynamic reports in OMS, WMS, and admin modules to track the KPIs and operational views you care about.
Query those custom reports programmatically via the Dynamic Reporting API to feed external BI tools or dashboards.
Configure dashboards with real-time operational metrics (orders, inventory, SLAs) tailored to roles or clients.
Use the public REST/SOAP APIs (orders, inventory, shipments, clients, items, etc.) to build bespoke integrations with ERPs, storefronts, and other systems.
Support both inbound (push orders, items, clients) and outbound (send tracking, inventory, order status) custom workflows via API.
Leverage third‑party integration platforms (e.g., NetSuite connectors, middleware, custom iPaaS flows) to orchestrate complex, multi-system scenarios.
Configure external cart/marketplace connections with mapping, default classes, and item-level options in partner tools like Order Desk or Extensiv.
Define role-based permissions and web service users with granular access for each merchant/client.
Configure API users and credentials per integration or client to isolate access and behavior.
Scale across multiple facilities and regions while applying different rules per site (e.g., routing, cut-off times, inventory rules).
Add new sales channels, brands, or clients and configure their unique workflows without changing the core platform.
Core behavior is primarily controlled by configuration, rules, and APIs; deep source-code level customization is not exposed as a standard option.
VeraCore offers structured training and ongoing support for new users through Advantive’s training and customer success organization.
Instructor-led training is available in virtual and onsite formats, tailored around the customer’s processes and role types.
Free, on‑demand product training (recorded sessions, tutorials, and documentation) is provided for self-paced learning and quick refreshers.
Formal discovery of training requirements is done upfront so the team can recommend the right mix of courses and delivery methods.
Core user training covers navigation, order entry, inventory management, receiving, picking/packing, shipping, billing, and client management needed for 3PL operations.
Admin and super‑user sessions typically include configuration, rules setup, integrations, and reporting, so internal champions can support local teams.
Training is designed to help customers “optimize their supply chain” and quickly realize value from VeraCore’s OMS/WMS capabilities.
Advantive provides a centralized customer support portal and knowledge base covering VeraCore and its related products.
Customers can access documentation, FAQs, and how‑to articles, as well as raise support tickets for product issues or configuration questions.
Product demos and refresher sessions can be requested as part of ongoing enablement for new staff or new modules.
New implementations typically include a guided onboarding program with training embedded into the project plan (discovery, configuration, testing, go‑live support).
Case studies highlight that, once the process is standardized, onboarding new clients onto a live VeraCore environment can be done in about a week in some 3PL scenarios, supported by repeatable training and setup playbooks.
VeraCore is delivered as a cloud-based SaaS platform under Advantive, so core security is handled at the application and infrastructure level, plus through ongoing patching of identified vulnerabilities.
Advantive states that it “continuously evaluates and enhances security measures” to prevent unauthorized access and maintain high cybersecurity standards for VeraCore.
VeraCore is a multi-tenant SaaS, which typically includes hardened hosting, network controls, and centralized patch management, although detailed control lists are not published publicly.
Multiple CVEs have been disclosed for VeraCore (for example, an unrestricted file upload issue and an SQL injection issue), and Advantive has released security updates and temporary mitigations, such as removing vulnerable upload functionality.
U.S. CISA has added these VeraCore vulnerabilities to the Known Exploited Vulnerabilities catalog, which drives priority remediation and patching requirements for U.S. federal-related environments.
Because public documentation on VeraCore’s detailed security controls (encryption at rest/in transit, certifications like SOC 2, etc.) is not available, customers generally need to:
Request a formal security and compliance package (e.g., security overview, pen-test summaries, certificates) directly from Advantive under NDA.
VeraCore uses a recurring, vendor-managed release cycle, with updates delivered to customers as part of its SaaS service.
Advantive publishes VeraCore release notes with explicit versioning (e.g., 2024.2.0, 2025.1.0, 2025.3.0), and notes that enhancements and changes are made available with a “monthly release.”
Security-related fixes (such as patches for CVEs) are also shipped in these versions, and critical issues can trigger additional patch releases (for example, 2025.1.1.3 for an SQL injection fix).
As a multi-tenant cloud/SaaS platform, VeraCore updates are applied centrally by Advantive, so customers consume new versions without managing their own installs.
Release notes are published in the Advantive support portal to explain new features, changes, and fixed issues, helping customers understand impact and adjust processes.
VeraCore runs under Advantive’s general data and privacy framework, which gives customers ownership of their data and some portability rights, but details depend on the Master Services Agreement (MSA) and privacy policy rather than a VeraCore‑specific public statement.
Advantive’s MSA defines “Customer Data” as the data a customer uploads to hosted services (which would include VeraCore), and commits that the provider will not modify customer data except to operate and improve the services or as requested for support.
The provider also agrees not to sell or otherwise disclose personal data in customer data to third parties for monetary or other valuable consideration, except where required by law or expressly permitted by the customer.
Advantive limits access to customer data to providing the software, addressing service or technical issues, improving functionality, generating de‑identified aggregated data, or handling customer support requests.
Onward transfer of personal data to unaffiliated third parties requires permission, except where disclosure is necessary for national security or law‑enforcement requirements, and Advantive remains responsible for appropriate onward transfers under EU–US data-transfer rules.
Advantive’s privacy policy states that individuals have a “right to data portability,” meaning they can obtain and reuse their personal data for their own purposes across different services.
The policy emphasizes that customers have full access to all data they submit to the platform and “sufficient access to respond to data subject requests,” which implies customers can extract or export their data from Advantive systems such as VeraCore.
Personal data processed by Advantive may be stored in the customer’s region, the U.S., or other countries where Advantive or its providers maintain facilities, with regional storage typically primary and cross‑region backups used for resilience.
When transferring personal data from the EU/EEA or the U.K. to countries without an adequacy decision, Advantive states it relies on mechanisms such as standard contractual clauses to maintain protections and data-subject rights.
Contractually, customers retain control over their own operational and personal data in VeraCore, while Advantive commits to restricted processing and no “sale” of personal data.
VeraCore contracts follow Advantive’s standard SaaS Master Services Agreement, which uses fixed subscription terms with auto-renewal and limited early-termination rights.
VeraCore is sold under an Order Form that specifies an initial subscription term (for example, 1–3 years) for the cloud service and support.
After the initial support/subscription period, services automatically renew for successive terms (often matching the prior term or as stated in the Order Form) unless the customer gives written non-renewal notice before the end of the then-current term.
The default non-renewal notice period for support services in the MSA is at least 90 days before the end of the current term, unless a different period is defined in the specific Order Form.
The MSA does not grant customers broad “termination for convenience” during a committed subscription term; instead, the main no-penalty exit mechanism is to give timely non-renewal notice so the service ends at term expiry.
If a customer wants to terminate support and later reinstate it, any reactivation is subject to mutual agreement and may involve a reinstatement fee determined by Advantive.
Advantive can terminate the agreement or access to services for material breach, which includes non‑payment, violation of use restrictions, or other significant contractual violations.
On certain customer breaches (e.g., failure to pay), all remaining unpaid fees for the then‑current subscription term become immediately due and payable (“acceleration”), meaning the customer generally still owes the full contract value for the committed term.
Advantive may also terminate all or part of the agreement if it reasonably determines that continuing to provide a specific component would infringe third‑party intellectual property, after attempting alternatives such as modification or replacement.
Advantive may terminate support services on at least 90 days’ written notice, even absent breach, although this does not automatically end the entire subscription unless stated.
If services or components are discontinued for IP or other reasons, Advantive may terminate those components on written notice, with the agreement describing this as a final step after trying workarounds.
On expiration or termination, each party must return or destroy the other party’s confidential information, with written certification of destruction if requested.
The MSA does not publish detailed public language on data export assistance or standard data-retention periods after termination; these points are typically handled via the Order Form, data-processing addendum, or negotiated clauses, so customers usually seek explicit commitments on export format, timelines, and any migration support.
Expect: multi-year contract, automatic renewal, 90‑day+ non-renewal notice, and no standard right to walk away mid‑term without paying remaining fees.
