...
A Catcher Seller operation is a vessel that catches and sells unprocessed or limited processed catch to individuals (e.g. via dockside sales) for personal consumption, or to other fishers for bait, but not for resale. Catcher Seller operations cannot do custom processing for others, nor can they have custom processing done for them.
Custom Processing Owner
Groundfish
The purchaser/owner of the seafood product may have another processor or operation receive, expedite, or process seafood on their behalf. The operation that is in possession of the seafood product, but not the owner or a direct agent for the owner is a Custom Processor. The eLandings interagency working group define NMFS defines a Custom Processor Processing relationship as between a processor, business, or entity that provides the service of seafood receiving, expediting, or processing but has not purchased (does not own) the seafood, and is not acting as an agent for the ownermothership or catcher/processor issued an FFP or a shoreside processor or SFP issued an FPP, with a contractual relationship with a custom processor to process groundfish on its behalf.
The owner of the catch must establish a custom processing operation for each physical plant that does the actual processing. This allows the owner of the catch to maintain visibility and control of the landing reports. The landing reports should be created and submitted on the owners behalf by users at the plant that are doing the custom processing. The owner of the seafood product must have a valid ADF&G Processor Code license and the processing facility will need to have their own receiving permits from Fish and Game as well as NMFS. These permits are used to establish the custom processing owner operation. Once the operation is established, the users at the custom processing facility will be authorized to make landing reports for the custom processing owner operation. This is akin to providing the custom processor with the metal process code plate to create paper fish ticket records.
The advantage of establishing the custom processing owner operation is that it gives the owner the ability to review and access landing reports electronically as soon as they have been successfully submitted to the Interagency Server. They can also remove the authorization to access those reports should the business relationship be terminated.
Crab
In this type of custom processing relationship, the owner of the crab must have their own established eLandings operation type that allows for custom processing relationships (see ADFG allowable activities matrix). Within that operation, they must have their own ADFG processor code in addition to an RCR permit. When the crab owner determines that they want to have a shoreside plant custom process for them, they must obtain an additional RCR permit that identifies the physical processing facility where the processing will occur.
The owner then creates the custom processing relationship in eLandiings, under Administer Operation. The process will generate a unique operation that identifies the relationship between the owner and processor and provide the user with an opportunity to add the new RCR before saving. eLandings administrators must approve these before users can access the new operation.
Child Operation Types
Two types of operations act as agents for another operation, but do not have any affect on the ownership of the seafood product. They pass the product along to their parent operation for processing.
...
A Buying Station is a land-based entity that receives unprocessed groundfish from a vessel for delivery to a shoreside processor and that does not process the fish (NMFS 679.2 Definitions). A buying station can be considered an annex of the plant or mothership (this is not done in Federal fisheries) for which it is acting as an agent. Buying Stations are usually completely shore based, such as a truck being loaded for transport to a distant plant, or may be a scow (a barge-like vessel). Tenders are no longer considered to be the same operation type as a Buying Station and were removed as a selectable child operation in eLandings back in 2016specifically added to shoreside operations so that tLandings and PTI can be configured and used to document tender vessel landings.
Tender
A tender operation vessel is a vessel that is attendant to catcher vessels and is used to transport or ferry unprocessed fish or shellfish received from another vessel to a shoreside an associated processor or mothership (not in Federal fisheries). This "child" operation is no longer considered a selectable operation type as it created too many database entries over time.(NMFS 679.2 Definitions).
User Accounts
Before a an operation can use the eLandings system to submit reports, they must establish a user account for each individual who will actually use the system. A user is an individual that has been designated to use the eLandings System to record seafood landings and production. Each individual that will use the eLanding System eLandings must be identified by name. The user management subsystem of eLandings controls which individuals are able to view and enter data on reports for specific operations. User accounts also allow the system to pre-populate some data fields on landing and production reports, such as processor codes, processor permit numbers, and port code.
...