Recognizing when 365 Kitchen Management implementation is
in scope
As of 7/31/25, FullCount Sales is selling 365 Kitchen
Management (formerly known as Kafoodle) as the "Dietary" part of
"FullCount Dietary and Nutrition Management".
So if you see a work order or quote that has "FullCount
Dietary and Nutrition Management" as a line item on it, know that it means
a) 365 Kitchen Management and b) the FullCount Nutrition License
feature-set. If you see a work order or quote that has "FullCount
Nutrition Management" as a line item on it, know that it means just the
FullCount Nutrition License feature-set but not including 365 Kitchen
Management.
Assigning 365 Kitchen Management Implementation
Specialist
When the 365 Kitchen Management system is in scope of a new
customer implementation or a side implementation, the FullCount Implementation
Project manager will want to request a 365 Kitchen Management implementation
specialist be assigned to the project team by emailing Stephen Kuhn
(
stephen.kuhn@365smartshop.com) to request this. The FullCount Project
Manager assigned should consider themselves as the over all responsible person
for delivery of the entire project, even the Kitchen Management implementation,
even though the Kitchen Management Implementation Specialist will do the bulk
of the work for the Kitchen Management part. No different than the
General Contractor building the house has subcontractors to do the plumbing and
the framing.
Kitchen Management <> FullCount Integration
When an organization has both Kitchen Management and
FullCount subscriptions, we consider them to also have the subscription rights
needed for the enablement of the integration between the two. They don't
necessarily have to have the two integrated, but they don't need to subscribe
to anything more to have the integration turned on.
To turn on the integration, the following must be done:
1a. The Kitchen Management Implementation Specialist needs
to set up an Integration user profile within the Kitchen Management
instance. The type of "user" that this user profile will be is
an integration type of user (in other words, not a human user). The KM
Implementation Specialist should communicate the email address, the API key,
and the KM Business ID for this integration user to the FullCount Project
Manager.
API Key is generated when the instance is created. This
number is only viewed once and cannot be found again. It MUST be recorded upon
creation.
KM Business ID is found under Home > Businesses >
Edit. The ID is visiable only in the URL of that web page.
Here is an example...
Darwin for your reference and integration:
Email:
API key:
meuvX9nYntdn3qyWsMEltwLfpExIPyDx1QX3RHLh
Business ID:
123
1b. Set the Community Nutrition Licensed flag to Yes and set
the Community Dietary System to Kafoodle.
3. Once Development completes the Redmine... verify that the
integration is working (create a dummy recipe in KM and see if it creates a new
Pending Item in FC for example)
Kitchen Management Business/Sites Org Structure and
Sub-Modules scoping
Handoff discovery questions below.
Outside of FullCount integration, Kafoodle is sold on the
basis of:
1. Modules they will have access to. Kafoodle kitchen
automatically includes ingredients, recipes and menus. Add-ons are: labeling,
stock and ordering, meal planning and EPMO
2. Business size and sites. Sites are either multiple physical locations
(e.g. Cafe 1, Restaurant 2, etc) or as we started to do for some FullCount
Clients: levels of care. (e.g. standard senior living vs intensive
care). Generally there is a split in recipes available in these
situations.
Example:
Business: Erickson Senior Living - Riderwood Village Silver
Spring
Site 1: Main Dining Room
Site 2: The Pub at Riderwood
Site 3: Memory Care
Site 4: Intensive Care
Exporting FC Items and importing into KM Recipes
Sometimes, you may want to export FullCount Items to then
import into Kitchen Management as Recipes. Then, once they are in Kitchen
Management as Recipes and have been assigned their IDs within Kitchen
Management, export these Recipes with their IDs to update the FullCount Items
to populate that Dietary System ID for each of the Items.
Here is a sample of a query to get FullCount Items
exported...
|
select i.item_code_id, i.code_description, i.menu_text
from t_menu_items mi, t_menus m, t_item_codes i
where
m.community_id = 7500
and
m.description like '%lassic%'
and
m.menu_id = mi.menu_id
and
i.item_code_id = mi.item_code_id
group by i.item_code_id, i.code_description, i.menu_text;
|
A sample import template for importing Recipes into Kitchen
Management can be found in ... J:\FullCount\FC - Implementations\The Hill
at Whitemarsh\Nutrition & Dietary Management Implementation.
??? instructions for how to import the KM IDs back into FC
Item records... a) Export Recipes from KM using one of the export templates
that include a column for the KM Recipe ID and also the column that we put the
FC ITEM_CODE_ID into (which is the Reference field in KM). For how to use
that export as the input to update the FC DIETARY_SYSTEM_ITEM_ID see
https://projects.fullcount.net/issues/17346
as an example???
in KM, the following export templates will include both the
KM IDs and the Reference Field (which represents the FC ITEM_CODE_ID): Full
preset (en_US), Full preset + full nutrition (en_US) and Full
preset without sub-allergens (en-US).
NOTE: this particular section of this documentation ought to
be changed upon the completion of Redmine 17671 (which, as of 10/22/25, is
scheduled to complete in Dec 2025 release)
FullCount Nutrition Feature-set Setup