How Ayoka connected Nuseed's seed production, processing, lot-level inventory, quality controls, and fulfillment workflows with Oracle NetSuite.
Grower contracts, field inspections, harvests, seed processing, laboratory results, warehouse inventory, and customer orders each create information that another team needs to act on. When those records are disconnected, a routine question can become a search across people, databases, and departments.
For Nuseed, the challenge was to connect the specialized work happening across the agricultural operation with the products, orders, warehouses, subsidiaries, and inventory transactions associated with Oracle NetSuite.
A lot's journey illustrates the complexity: Where did the seed originate? What processing did it undergo? Has quality approved it? Which warehouse holds it? Is it available for a particular order? Will the actual shipment reconcile with the ERP?
The value is in carrying the right business relationships through every handoff, from the field to the customer.
Different teams need different tools. The design connected specialized agricultural workflows to relevant NetSuite records instead of forcing every operational step into a generic ERP screen.
The application uses NetSuite-linked identifiers and integration middleware so field activities, inventory, quality events, and order movements can remain associated with the correct enterprise records. The implementation includes Celigo-based transaction flows and a separate Jitterbit invoicing flow.
Records can fail to sync or require reconciliation. SMP includes transaction-state tracking, an administration view, error notifications, and controlled retry functions. That operational follow-through is an important part of maintaining useful integration.
Ayoka developed the Seed Management Platform (SMP), purpose-built operational software connected with NetSuite-linked enterprise data and transactions.
Associate grower contracts and products with planting activity, field inspections, estimated yield, and actual harvest events.
Follow jobs through drying, sizing, blending, treating, packaging, and other processing steps, including input/output lots and status.
Maintain lot identity, movement history, warehouse locations, physical counts, and comparisons against NetSuite inventory snapshots.
Connect test results, approvals, release decisions, and nonconforming inventory to the lots and movements affected.
Link sales and transfer orders to actual pick lists, shipped lots, pallets, dispatch records, and warehouse receipts.
Record transaction states, flag failed synchronization, and support authorized review or retry of affected records.
The Seed Management Platform (SMP) is a web-based, subsidiary-aware operating system for seed production and inventory. It links agricultural field activity, lot-level stock management, quality-control tests, processing operations, and dispatch workflows to Oracle NetSuite ERP through integration middleware and direct application endpoints.
The defining characteristic is transaction-level continuity: a grower field and planned harvest can become lots, stock movements, processing outputs and fulfilled sales or transfer orders, with product, warehouse, subsidiary, and order references carried into NetSuite-facing messages.
Processing status, timing, input and output lots, and related orders can be reviewed together.
Physical counts and lot-level records can be compared with NetSuite inventory snapshots.
Origin, quality, inventory movement, and fulfillment details remain associated with relevant lots.
Production Management revolves around GrowerContractField. A field record links planting rows and NetSuite products to geographic/area attributes, production manager, growing season, contract references, inspection results and harvest records. FieldInspection captures condition, estimated yield, location, agronomic observations, insects, weeds, diseases, off-type counts and nonconforming flags. Mobile APIs expose inspection-related operations.
The production-management controller and inventory services connect harvested output to LotLocationPreliminary and Lot/LotLocation. NetSuiteEndpointHandler.Production distinguishes harvest from production, supplies contract quantities in contract UOM where available, and splits conforming from quarantine output. The output is traceable to source field/processing job and lot references.
ProcessingJob stores status, importance/priority, input/output preliminary records, vendor, source and processor warehouses, related sales order, expected/actual dates and documentation. ProductionType covers drying, scalping, blending, sizing, treating, packaging, reworking, mixing cultivar, crushing and planting harvest, among others. These workflows support operational WIP visibility and conversion tracking; a separate NetSuite financial WIP cost-ledger interface is not presented.
Lot is the persistent seed identity (internal/customer lot number, item reference, quality values); LotLocation is the transaction/location record (quantity, warehouse-local location and bin, current flag, parent/child history, quarantine/nonconforming status, production source, transaction links and synchronization state). This separation is central to how SMP supports traceable stock movements over time.
Warehouse-specific Location records can be marked Internal, distinguishing SMP-only storage from ERP-reconciled locations. Quarantine conditions may map inventory to a nonconforming child NetSuite warehouse when preparing ERP stock/status transitions. PhysicalCount saves counts at the location level and provides printable CSV audit reports.
Inventory reconciliation: NetSuiteInventoryReport groups both sources by product and warehouse, translates SMP quarantine to the correct nonconforming warehouse, calculates SMP physical and available quantities, and exports NetSuite on-hand, available, in-transit and on-order comparisons with as-of dates.
| Metric | Implemented calculation or metric |
|---|---|
| SMP physical quantity | Sum of current lot-location quantities for non-internal locations, with quarantine warehouse mapping. |
| SMP available quantity | Physical quantity less the application’s assigned quantity. |
| NetSuite on hand / available | Stored NetSuiteInventory.OnHandCount and AvailableCount. |
| Variance / difference | SMP physical quantity minus NetSuite on-hand quantity; formatted for the CSV report. |
| Additional context | NetSuite in-transit and on-order quantities, inventory snapshot AsOfDate. |
Test submissions may be associated with a lot, lot-location or preliminary lot and can include test parameters, result dates, notes, documents, expiry, release-authorization approvals, an approval key and approver comments. Test templates and generation-aware test filters are implemented as part of the current application.
The release-authorization flow has UI endpoints to present approval lists and approve/reject a submission; the application can retain requester/approver context and notify participants by email. Lot-level quality data can also be sent to NetSuite by the Celigo QualityControlTestResults operation.
SupplyAssessmentRating is persisted against inventory lots/locations and field inspections. A score can follow field-to-lot and lot-processing pathways under business-specific rules. This indicates operational gating and triage for quality/timing—not just passive test storage. Quarantine and nonconforming values are explicitly represented in receipt/production/fulfillment quantities.
ShippingManifest manages order-linked dispatch records with shipping state, method, carrier, route, shipment date, tracking information, check-off lists and documents. PickList ties shipped lines to sales-order or transfer-order product lines, specific lots/locations, bins, packing positions, pallet quantities and invoice number. The user-facing views include sales and transfer shipping, receiving, pallet controls, packing lists, dispatch docket, pallet sticker and bill-of-lading generators.
The outbound NetSuite fulfillment is built from the real shipped lot movements, with sales/transfer order ID, line number, warehouse, lot-level quantity and quality, and pallet information. The inbound NetSuite callback resolves the transaction by SMP manifest ID, NetSuite order ID and date and updates the interface state, with sales invoice numbers stored where returned.
For interwarehouse transfer, the application implements both sending and receiving steps. A completed outbound fulfillment callback is used to invoke the corresponding inbound NetSuite transfer receipt for matching positive-side inventory records. This creates an explicit two-leg process rather than treating a warehouse transfer as a single local edit. Transfer-order records also include a consignment-customer relationship.
The central Import screen validates the permitted import type, captures the uploaded file and creates a ProcessedFile record identifying user, subsidiary, filename, time, record count and error log. Hangfire then queues the corresponding import worker. Current ImportType values include Grain Trader, Grower, Harvest Declaration, Purchase, Test Submission, Test Template, Internal Transfer and Non Conforming.
The application also supports screen-specific CSV import/export and report generation. Report classes produce inventory variance, lot history, production/processing information, pick/dispatch paperwork, test reports and physical count exports. The report system is operationally useful both for user review and for downstream spreadsheet-based analysis.
| Report / output | Implemented functionality |
|---|---|
| Inventory reconciliation | SKU/warehouse inventory comparisons and variance exports. |
| Lot history | Lot movement and transaction history reporting. |
| Processing job reports | Processing job status, inputs, outputs and production reports. |
| Shipping documentation | Dispatch summaries, packing lists, pallet stickers and bills of lading. |
| Physical counts | Location-level physical-count quantities and CSV exports. |
| Test and product reports | Quality-control, test and product/inventory reports. |
The application uses an Entity Framework Code First domain model and schema migrations. The diagram below selects integration-critical relationships instead of listing every entity. Cardinalities represent logical one-to-many relationships; several paths have optional foreign keys.
| Entity | Key attributes / relationships |
|---|---|
| NetSuiteProduct | ItemCode, ItemName, Generation, Classification, StockNetSuiteUnitOfMeasureId, NetSuiteProductComponents. |
| Lot | LotNumber, CustomerLotNumber, NetSuiteProductId, QualityData, QualityDate, AlternateSeedSize. |
| LotLocation | Quantity, CreatedDate, LotId, LocationId, Bin, NonConformingSource, InterfaceStatus, InterfaceErrorDetails. |
| LotLocationPreliminary | Expected/actual quantity, origin and source references, planned/processed/harvest linkage. |
| NetSuiteWarehouse / Location | NetSuiteSubsidiaryId, child nonconforming warehouse; Location.Internal and SubNetSuiteSubsidiaryId. |
| ProcessingJob | Importance, ProcessingJobStatus, warehouse/order links, commence/complete dates; output preliminaries. |
| ShippingManifest / PickList | Manifest state, shipping dates, product order lines, lot/bin/pallet detail. |
| TestSubmission | Lot/LotLocation links, parameter results, IsApproved, ApproverComment, expiration and approval key. |
| NetSuiteInventory | AvailableCount, OnHandCount, InTransitCount, OnOrderCount, AsOfDate, SKU and warehouse FK. |
The following panels are illustrative reconstructions of current user-interface structure and controls. They are not live application screenshots, and sample grids intentionally contain no customer production records.
NetSuite Sync provides visibility into ERP snapshot range and transaction failures; each actionable transaction category is shown conditionally when it contains records. Record rows link to related business transactions and show sync dates and interface error details. A retry action is permission-gated.
The Lot Inventory screen has warehouse/location/product/lot and classification filters, a NetSuite-vs-SMP Only location selector, report generation and role-restricted CSV uploads. The table is derived from lot-location quantities and quality/status fields.
The application supports new processing jobs, unfinished/finished filters, priority/importance, warehouse, product and production types, expected vs actual dates, input/output items, document uploads, reports and NetSuite production messages.
Production Management provides searchable field/production entries, report selection, CSV upload and links into planning, planting, inspections and harvesting. Production fields link NetSuite products and grower contracts to subsidiary-aware field data.
Order-linked shipping workflows support state and warehouse filters, creation, dispatch paperwork, pallets, pick lists, shipping documents and transfer receiving. The actual fulfillment payload is built from inventory movement events.
Tests, result checks, documents, release authorization, approver comments, lot/lot-location linkage and quarantine states are supported by the current model and controllers. Exact composite presentation varies by test/detail and approval page.
Questions we hear from businesses with specialized workflows that extend beyond their ERP.
Nuseed demonstrates Ayoka's experience connecting complex workflows to the enterprise systems a business already uses. Ayoka's B.O.S.S. Business Operation Software System applies an integration-first approach to production visibility, inventory, quality, handoffs, and operational decisions.
Through Ayoka's Rent Custom Software model, clients can acquire tailored integrations and operational capabilities without commissioning a conventional large upfront software build.
This is an Ayoka custom integration case study, not a claim that Nuseed purchased or deployed B.O.S.S.
We'll start with the process, the data you have, and the decisions your team needs to make.
Start a conversation Explore B.O.S.S. →Tell us what you’re seeing. We’ll start with the operational problem and help determine what is getting in the way.
